Engagement & pricing
Clear starting points.Scope before commitment. Start small enough to measure. We agree the workflow, deliverables and costs before you commit to a larger implementation.
Choose a useful first step. These are starting scopes. Your estimate depends on the work involved, rather than a fixed bundle of unrelated features.
Workflow assessment Find a useful first step.
For a repeated task or operational delay that needs a clearer plan.
Scope to agree Current-process map and constraints Candidate automations and integration checks Assumptions, risks and a recommended pilot Useful for: An existing business deciding where to start.
Discuss an assessment Automation pilot Test one defined workflow.
A limited implementation to evaluate usefulness before a larger commitment.
Scope to agree One agreed workflow and defined connections Human approval and exception handling Testing, documentation and handover Useful for: A team with a repeatable process and access to its tools.
Scope a pilot Knowledge or support pilot Make approved information useful.
A narrow assistant for a defined set of documents or customer questions.
Scope to agree Agreed sources and access boundaries Source references and human handoff Answer-quality checks and usage review Useful for: A team with useful, maintainable business content.
Discuss an assistant Business website launch Build a clear digital foundation.
A focused website that explains your offer and gives customers a practical way to enquire.
Scope to agree Agreed pages, content and customer journey Responsive layout and enquiry handling Launch checks, editing and handover Useful for: A new business or a business replacing an inadequate site.
Plan your website Web application or MVP Build the essential user journey.
A scoped application for a specific customer or operational need.
Scope to agree Defined users, permissions and core features Agreed data flows and integrations Testing, deployment and documentation Useful for: A business with a defined need beyond a website.
Discuss an application Ongoing improvement Keep the solution useful.
A support plan matched to the systems, people and work involved.
Scope to agree Agreed monitoring and maintenance Bug fixes, training and change capacity Defined support hours and exclusions Useful for: A team maintaining or improving an existing solution.
Plan ongoing support What changes the price? The workflow, features, data preparation, number of integrations, user volume, review requirements and ongoing support all affect cost. Third-party software, AI usage, messaging and hosting fees are identified separately where applicable.
Know what you’re agreeing to. Your written proposal should set out deliverables, exclusions, responsibilities, payment stages, review points and timing. For ongoing support, agree the included capacity, response arrangements and how additional changes are priced.
No full technical brief is needed for the first conversation. Tell us the problem and what is already in place.