How we take your project from idea to launch.

Our owner reviews your enquiry. We reply with any useful questions and may suggest a call. If your idea is still taking shape, start with the problem you want to solve and who needs help.

Timing depends on the features, content, integrations, testing and review process. We confirm available skills and a realistic start, then include the delivery stages and assumptions in the proposal.

Yes. Share the request when you identify it. We review how it affects the agreed work, price and schedule, then agree the next step before making the change.

Raise the concern at a review point or as soon as you notice it. We compare the work with the agreed requirements, decide what needs correcting or changing, and record any effect on delivery.

We can review a confidentiality agreement (NDA) before sensitive details are shared. The project agreement should also explain who can access the information and how it will be handled.

The project agreement defines code ownership, access to accounts and code repositories, and the documentation included. We agree these responsibilities and the handover so you know what you will receive.

Yes. We can work with an in-house team, agency or other delivery partners. We agree who does what, the tools and meetings we use, and how work is reviewed and handed over.

Depending on the engagement, the proposal can use milestone or periodic payments. The amounts, payment dates, approval points and process for changes are agreed before work starts.

Before launch, we agree access, documentation, any warranty and the work included in ongoing support. Maintenance and new improvements are scoped for your project, so you know what is covered and what needs a separate agreement.