Our engagement model
You should not try to fully price implementation before you understand the data model and integrations. The better pattern is to sell the uncertainty-reduction work as a paid phase, then price the build from that.
Free qualification → paid discovery/design → priced implementation 1. Free qualification call
A short conversation to understand the shape of the project and give you a rough range. No commitment, no cost.
What we cover:
- What business process is being automated or built?
- Which systems are involved?
- Is there API access, database access, files, webhooks, or manual exports?
- How critical is the initiative?
- What happens when data is missing, duplicated, delayed, or rejected?
- Who owns the source systems and can give access?
- What is the expected business value?
What you get: A rough order-of-magnitude range and a recommendation on next steps.
2. Paid discovery
A fixed-scope, fixed-fee engagement that makes implementation estimable. The goal is not to build — it is to remove uncertainty.
Typical duration: 1–3 weeks
Deliverables include:
- Process map: current workflow, target workflow, exceptions
- Systems map: source systems, target systems, ownership, access methods
- Integration plan: APIs, webhooks, database access, files, queues, auth
- Data model: entities, key fields, IDs, mappings, validation rules
- Risk register: unknown APIs, bad data, permissions, performance, security
- Backlog: user stories or work packages with acceptance criteria
- Implementation options: MVP, standard, robust
- Build estimate: range, assumptions, exclusions, recommended pricing model
Important: At the end of discovery, you have a technical design you can use whether or not you build with us. This is the safest first contract.
3. Implementation
After discovery, we choose the right pricing model based on remaining uncertainty.
Time and materials with a cap
Best default when integrations or data quality still have unknowns. You get transparency and control; we avoid pretending certainty exists.
Fixed-price milestones
Good for contained work when the data model, system access, and acceptance criteria are well understood after discovery.
Fixed budget, variable scope
The client fixes the budget and deadline; we jointly prioritize the backlog. Often better than "fixed scope, fixed price, fixed deadline".
Monthly retainer
Useful for ongoing automation, integration, and improvement work. A monthly capacity block with a prioritized backlog.
How we decide the approach
- High uncertainty + high integration risk: Paid discovery, then time and materials with a cap.
- Medium uncertainty: Fixed discovery, then fixed-price milestones with stated assumptions.
- Low uncertainty + repeated pattern: Packaged fixed price.
- Long-term stream of work: Retainer or dedicated capacity.
The best teams do not win by estimating perfectly at the start. They win by making uncertainty visible, charging for the work that removes it, and structuring contracts so both sides can make good decisions as they learn.
Ready to start?
The data model and integration design are exactly the risky parts. Rather than guessing, we propose a short paid discovery phase. At the end, you will have a technical design and a realistic build estimate.