Pricing
Transparent pricing for scoped automation
We work on fixed-scope engagements. You know the price, the deliverable, and the success metric before we start. No retainers until you've seen results.
Fixed scope
before build starts
2–4 months
typical payback on strong workflows
48 hours
written estimate after scoping call
How pricing works
Buy the first proof point, not a vague transformation
Scope the workflow
We map one operational bottleneck, the systems involved, the review layer, and the success metric before any build work begins.
Agree the pilot
You get a defined deliverable, fixed price, deployment path, and control model. No vague roadmap, no open-ended discovery phase.
Review the result
Once the workflow is live, we review the operational outcome and only then decide whether expansion makes sense.
Engagement types
Choose the right starting structure
Pilot
From €4,000
Best for one workflow in 6–8 weeks
Start with one bottleneck, one KPI, and one controlled deployment path. This is the right choice when you need proof, not a transformation programme.
Works well if
Best when the workflow is clear, repetitive, and already costing your team real time every week.
- Scope session and workflow mapping
- One end-to-end workflow build
- Human review checkpoints
- Rollback and handoff plan
- Post-pilot performance review
Focused Build
From €12,000
Best for 2–4 connected workflows
Use this when the first workflow depends on adjacent systems, routing logic, or multiple teams. It is still scoped, but broader and more integrated.
Works well if
Best when multiple handoffs break together and solving one workflow in isolation would leave too much friction behind.
- Everything in Pilot
- 2–4 connected workflow deployments
- Cross-system routing and integration logic
- Internal playbooks and team enablement
- Monitoring and iteration across the build window
Partnership
Custom
Best after a proven pilot
For teams that want ongoing delivery capacity after the first workflow is working. This is for expansion, refinement, and new workflow rollout over time.
Works well if
Best when you already know the operating model works and want a senior team to extend it without rebuilding context each time.
- Monthly delivery and iteration capacity
- Priority access to the team
- Workflow health monitoring
- Quarterly ROI and performance review
- Expansion planning across new automation targets
All prices are indicative. A free scope call produces a precise written estimate for your specific workflow.
What every engagement includes
- Workflow mapping and scope definition
- Review checkpoints before risky actions
- Deployment path aligned to your current stack
- Documentation and operating handoff
- Performance review after rollout
- Honest fit assessment before any commitment
What this is not
- Large undefined transformation programmes
- A multi-year consulting engagement before delivery
- Platform replacement across your full stack
- A promise to automate everything at once
Pricing FAQ
Questions before you commit
What changes the price most?
Usually three things: how many systems the workflow touches, how much custom logic is needed, and how clean the underlying data is. The scoping call is where we convert that into a fixed written estimate.
Why start with one workflow instead of a bigger roadmap?
Because one strong workflow proves the operating model faster than a broad abstract plan. It gives your team something measurable, controlled, and useful in production before you commit to anything larger.
What happens if we are not the right fit?
We tell you on the scoping call. If the timeline is too open-ended, the scope is still vague, or the workflow is not yet a good automation candidate, we would rather be direct than sell the wrong engagement.
What is included in every engagement?
Scope session, build, review controls, deployment plan, rollback logic where needed, handoff documentation, and post-launch performance review. We do not treat delivery and governance as separate extras.
When does a partnership make sense?
Usually after a pilot or focused build is already working. Once the team trusts the operating model, a partnership becomes the efficient way to expand without repeating discovery from scratch.
Not ready for a call?
Describe the workflow — we'll reply with a written estimate
Skip the meeting. Tell us what the manual process looks like today, and we'll send back a scoped estimate you can forward to your team.