Services
AI AutomationDigital TransformationConnected SystemsFractional CTOMVP Launch Sprint All services
Case studiesToolsBlogAboutContact Request a strategy call
Self-assessment

How much delivery time should you plan for?

Pick the engagement type and scope for an indicative effort range in delivery weeks. No price is shown here — pricing follows discovery, requirements review and a written proposal.

What are you planning?
Scope
Indicative effort
5–9 weeks
One workflow designed, built and running in production with a limited scope.
Effort ranges assume decisions are available on your side, that the systems involved expose a usable integration route, and that data quality is workable. Any of those being untrue moves the range.
Send this to yourself and start a scoping conversation:
One email with your results. No newsletter, no spam.
Pricing is determined after discovery and depends on workflow complexity, integrations, data readiness, scope, timeline, and support requirements.

How to read this tool

  • You entered Figures you typed or selected. Nothing is pre-filled from client data.
  • Illustrative assumption A planning percentage you control. Not measured across client engagements.
  • Calculated output Arithmetic applied to the two rows above, shown in full below.
  • Verified client result None. No figure in this tool comes from a client engagement.

This tool provides an illustrative planning estimate based on the information and assumptions entered. It is not a forecast, quotation, professional advice, or guarantee of business results.

This estimate is for early planning only. It is not a quotation, commitment, or guarantee of delivery scope, timeline, cost, or business outcome. Final pricing follows discovery, requirements review, integration assessment, and a written proposal.

How the estimate is calculated

  • Each project type carries a base effort range. That range is scaled by the scope you select and extended by the number of systems to be integrated.
  • Effort is expressed in delivery weeks, not in cost. No price range is shown, because no published rate card applies across these engagement types.
  • Ranges assume decisions are available on your side, that the systems involved expose a usable integration route, and that data quality is workable.
  • Your budget selection is recorded as your expectation. It does not affect the effort range shown.
  • Pricing is determined after discovery and depends on workflow complexity, integrations, data readiness, scope, timeline, and support requirements.
WhatsApp us