How it works

A clear path from idea to delivery.

Start with a conversation and a written proposal. Then plan, build, and review the software together, whether we are working on an ongoing basis or towards a defined project handover.

Book a call See the process

We agree on what will be delivered, how you will review it, and what support you need after launch.

01 / From discovery to support

From the first conversation to working software

For ongoing development, planning, building, and releasing repeat as your priorities evolve. A defined project follows an agreed scope through to handover.

Conversation & proposal

Discuss your goals, existing software, budget, and timing. Identify what needs investigation before a delivery commitment can be made.

A free introductory call to assess fit
Review of the starting point, priorities, and dependencies
A separately priced assessment if deeper investigation is needed
Agreement on scope, fee, payment schedule, and start date

What you get

A written proposal for ongoing development or a defined project. The engagement starts after agreement and initial payment.

Plan & build

Build in small, reviewable steps with feedback from the people who will use the software.

A shared delivery plan with agreed priorities
Weekly reviews of working software, decisions, and blockers
Direct communication with Dimo
Changes discussed with their effect on scope, price, and timing

What you get

Visible progress and a shared understanding of the next priorities.

Ship

Prepare the software for its real environment and the people who depend on it.

Production hardening and performance testing
Security review
Deployment to your infrastructure
Monitoring and alerting setup

What you get

Software running in production, handling real users.

Support

Complete the handover and agree on what ongoing support looks like.

Documentation and knowledge transfer
30-day warranty for bugs in agreed project deliverables
Continued development under an ongoing engagement
Agreed support scope and responsibilities

What you get

Documentation, knowledge transfer, and an agreed support plan.

02 / Communication

Communication during your project

A weekly review

Review progress, priorities, and blockers each week. Agree on the communication channel and who can make decisions at the start.

Review working software

Use demos and practical feedback to test whether the work is meeting the intended need.

Raise risks early

Discuss blockers, dependencies, and scope questions while there is time to make a considered decision.

03 / How we use AI

How we use AI in development

AI tools can support implementation, exploration, and testing. The requirements, technical decisions, and acceptance of the work remain an engineering responsibility.

We agree on the tools and data handling requirements for your project, including any restrictions on code or information shared with third-party services.

Technical decisions guided by project requirements
Code review and testing before delivery
Explicit permissions for sensitive data and tool use
Documentation your team can understand

Tell us what you’re working on.

Share your priorities, budget, and the current state of the software. We’ll discuss the scope and how an engagement could work.

Tell us about your project Or book a conversation