Company Context
You’re the PM for LedgerFlow, a B2B SaaS platform that automates accounts payable (AP) workflows for mid-market and enterprise companies (invoice capture, approvals, PO matching, ERP sync). LedgerFlow is Series C, does $85M ARR, and serves 1,200 customers. The product is API-first, with a configurable workflow engine used by 70% of customers.
LedgerFlow’s differentiation vs. Coupa and SAP Ariba is faster time-to-value: median implementation is 6 weeks (vs. 12–20 weeks for legacy suites). Your gross margin is 78%, but professional services margin is only 15% and trending down as custom work increases.
Scenario
A strategic customer, Northwind Medical Group (NMG), is a healthcare provider network with 180 clinics across 12 states. They process ~220,000 invoices/month and are currently on an older on-prem AP tool. NMG is in the final stage of procurement for a 3-year, $2.4M ARR contract (your largest deal this half).
NMG’s procurement director is requesting a bespoke customization:
- A custom “Clinical Exception Routing” workflow: invoices tied to certain clinical cost centers must route to a rotating on-call approver pool, with escalation rules based on shift schedules.
- A custom “Vendor Credential Gate”: invoices from medical suppliers must be blocked unless the supplier’s credentialing status is valid in NMG’s internal system.
- A custom “Audit Packet Generator” that exports a PDF bundle in a specific format required by their external auditor.
Sales is pushing hard to say yes to close the deal. Engineering is concerned that this will fork the workflow engine and create long-term maintenance overhead.
What You Know (Data + Research)
Current product capabilities
- Workflow engine supports: conditional routing, approval groups, SLA timers, escalations, and webhooks.
- You have a standard integration framework (REST + event bus) that can call external systems for validation.
- You do not have a shift-scheduling module; building one would require a new domain model and UI.
Customer discovery notes (from Solutions Consultant)
- NMG’s underlying job: “Ensure invoices are approved quickly without violating compliance.”
- Their current pain: late approvals cause missed early-pay discounts; they estimate $1.1M/year lost.
- Their compliance team is risk-averse after a recent audit finding; they want “no manual steps” for credential checks.
Business and product signals
- In the last 12 months, 14% of enterprise deals requested custom workflow logic; only 3% of SMB deals did.
- Custom work has increased support tickets: customers with customizations generate 2.6× more P1 incidents.
- Churn risk: enterprise logo churn is low (2.5% annually), but NRR is sensitive to implementation timelines.
Competitive landscape
- Coupa will build custom workflows but typically requires a longer SI-led implementation.
- A newer competitor, Ramp Bill Pay Enterprise, is winning deals by emphasizing “configuration over customization” and faster rollout.
The Problem
You need to advise NMG against at least one of the requested customizations in favor of standard configuration and/or integrations, while still:
- Protecting the deal and renewal likelihood
- Maintaining LedgerFlow’s product strategy (configurable platform, not bespoke implementations)
- Meeting healthcare compliance expectations (HIPAA-adjacent controls, auditability, least-privilege access)
Your Tasks (Deliverables)
- Clarify the real user needs behind each customization request using a Jobs-to-be-Done lens (who is the user, what outcome, what constraints).
- Propose a recommended approach for each of the three requests:
- Standard configuration (existing features)
- Configuration + integration (webhooks/API)
- Productized roadmap item (generalizable)
- Decline / defer (with mitigation)
- Prioritize what you would build vs. configure using a structured method (e.g., RICE + “reusability” factor, or Kano for enterprise value).
- Draft how you would communicate the pushback to NMG and Sales: what you say, what you offer instead, and how you de-risk their concerns.
- Define success metrics and an experiment/validation plan for the chosen approach (implementation time, incident rate, approval latency, etc.).
Constraints
- Timeline: NMG needs a signed SOW in 4 weeks and go-live in 12 weeks.
- Resourcing: You have 6 engineers total on the workflow team; only 2 can be allocated to NMG-specific work without slipping Q3 commitments.
- Architecture: You cannot introduce a customer-specific fork; all changes must be behind config flags or be generally reusable.
- Compliance: Any solution must produce an auditable trail of approvals and credential checks; access must follow least-privilege.
What Good Looks Like
At the end, you should have a clear recommendation that balances customer value, platform integrity, and business impact—showing how you’d avoid bespoke customization while still solving the underlying problems NMG cares about.
