Skip to content

Trust & guarantees

What you can hold us to.

Hiring a software team is a trust decision. Here is what we commit to in writing, how your project and data are protected, and how you can check us before you sign.

This page summarises our standard way of working. The binding terms for your project are in the written agreement we sign together.

Our commitments

Six promises that shape every proposal and agreement we write.

  • Scope and price in writing

    After discovery we agree scope, milestones and timeline in writing before development starts. Changes are quoted and approved before work begins, so there are no surprise invoices.

  • You own what you pay for

    The code we write for your project is delivered to a repository in your name, with documentation, and your data stays yours. Third-party and open-source components keep their own licences, and we list them for you.

  • A warranty on our work

    Defects in what we deliver are fixed at no charge during a warranty period stated in your agreement. Problems caused by changes made by others, or by new requirements, are handled as separate work.

  • Security built in

    Code review, testing and security checks run throughout delivery, not at the end. Access is limited to the people who need it, and secrets stay out of source code.

  • Honest, visible progress

    One point of ownership, a working release to review every cycle, and straight answers when scope, risk or timeline changes.

  • Confidential by default

    We treat your idea, data and documents as confidential. A signed NDA is available before you share details, and we name clients or show their work only with their permission.

What you receive

Ownership and handover

Software you cannot move is a risk. We plan for the day you want to take it elsewhere, even if you never do.

  • Source code in a repository in your name
  • Documentation: setup, architecture overview and deployment notes
  • Hosting, domain, app store and third-party accounts registered to you
  • A walkthrough session for your team or the next developer
  • A list of third-party and open-source components and their licences

How we reduce the risks buyers worry about

These are the concerns we hear most, and what we do about each.

  • The scope keeps growing

    Scope is written down, and changes are quoted and approved before work starts.

  • The price changes midway

    Estimates follow a discovery workshop, and we tell you early if scope or risk moves.

  • I cannot see what is happening

    A working release to review every cycle, and one person accountable for updates.

  • The quality is poor

    Code review and testing run throughout, and defects are covered by the warranty period.

  • I will be locked in

    You receive the code, documentation and access, so another team can take over.

  • It breaks after launch

    A controlled release with monitoring and a rollback plan, then a maintenance agreement with agreed response times.

  • My information leaks

    Confidentiality terms, least-privilege access and careful handling of data.

Security and privacy

Security is part of delivery. These are the practices we apply, and the checklist behind them is public.

  • Code review and automated tests before every release
  • Access limited to the people who need it, with strong authentication
  • Secrets and credentials kept out of source code
  • Encrypted connections (HTTPS) for every public application
  • Backups set up as part of launch
  • Dependencies kept up to date under a maintenance agreement

This website sets no advertising or analytics cookies and stores only the data needed to answer your enquiry. Read the Privacy Policy

Check us before you sign

You should not have to take our word for it.

  1. 01

    Look at the work

    Browse our case studies. Detailed walkthroughs are available on request.

  2. 02

    Talk to people we have built for

    Ask for references. We arrange conversations with clients who have agreed to take them.

  3. 03

    Test our thinking

    Our guides and free tools show how we scope, price and plan before any contract.

  4. 04

    Meet the team

    Ask who will build your project, and speak with them before you sign.

Things we will not do

Things we will not do

  • Promise a delivery date before the scope is understood

  • Publish client names, logos or quotes without written permission

  • Invent testimonials, ratings or certifications

  • Hold back your code, domain or data

  • Start extra work you have not approved

Questions

What buyers ask us about trust.

Who owns the code you write for us?

You do, as set out in your agreement. The code written for your project is delivered to a repository in your name with documentation. Third-party and open-source components stay under their own licences, and we list them.

Is there a warranty on the work?

Yes. Defects in delivered work are fixed free of charge during a warranty period stated in your agreement. After it ends, a maintenance agreement covers fixes, updates and support.

What happens after launch?

Launch is a controlled release with monitoring and a documented handover. You can continue with us under a maintenance agreement with agreed response times, or take the system over yourself.

Can we sign an NDA before sharing our idea?

Yes. Tell us you would like one when you get in touch and we will sign before you share details.

Can I speak to a past client?

Yes. We arrange reference conversations with clients who have agreed to take them. Ask when we discuss your project.

What if I want to move to another team later?

You can. Because you receive the code, documentation and access, another team can take over, and we will support a clean handover.

Have a question before you start?

Ask us anything about scope, ownership, warranty or security. We will answer plainly.