How we work
A clear scope, a fixed price, and working software you own. This page explains how each of those is kept, including how we use AI and what a person always checks.
How a project runs
You tell us about the problem.
Through the enquiry form or by email. Every genuine enquiry gets a reply by email within two working days. If it is not something we take on, the reply says so and, where we can, points you to a better option.
A short call, if it looks like a fit.
We ask what happens today, what goes wrong and who decides. It is a conversation, not a pitch. At the end we recommend one of three things: a package with a fixed price, a paid discovery, or someone better suited.
Paid discovery, for anything larger than a package.
An Automation Audit or a Discovery Sprint (see below) that ends with a fixed price.
A proposal.
Fixed price, milestones, what is included, what is not, and how changes are handled. It is valid for 30 days.
The build.
In milestones, with a working preview you can click through at each one. You talk to the engineer doing the work, not a go-between.
Launch and handover.
Tests, documentation, accounts in your name, and a walk-through for your staff. Then a care plan, or a Handover Pack if you would rather run it yourself.
Paid discovery
Fixed prices only work when the work is understood. Discovery is how we get there, and it is useful to you whether or not we build what it describes.
Automation Audit: £750
Five working days. We look at one area of admin (for example enquiries, invoicing or reporting), map the steps and the systems, estimate the time the work takes, and recommend what to automate first, with a price for it.
Discovery Sprint: £2,400
Two weeks, ending with a written pack and a 60-minute readout. You get:
- A map of the process and data in scope, with the time or cost of the problem estimated.
- Requirements in priority order: must have, should have, later.
- The technical approach, the systems it connects to, and where it will be hosted.
- A data protection and risk note covering personal data, user roles and any use of AI.
- Clickable wireframes of the three to five key screens, or a working prototype of one flow.
- A fixed price, milestones and a timeline for the build, valid for 30 days.
£1,000 of the Sprint fee is credited against the build if you sign within 30 days.
The Sprint does not include production code, writing your content, or research with more than five interviews.
If a listed output is missing, tell us within 14 days of delivery; if we have not supplied it within 10 working days, we refund the fee. See our commitments.
Prices exclude VAT. Tibyan Labs is not currently VAT registered, so no VAT is charged.
Fixed prices and changes
- The price in the proposal is the price for what the proposal describes.
- Anything new is written up as a change request with a price, and nothing is built until you agree it.
- If a project goes quiet for 10 working days, it pauses and we agree a new start date together.
- Small tweaks under half an hour during a build are not charged.
Our commitments
Four commitments, each with its limits stated next to it.
1. The price we agree is the price you pay
The price in your signed statement of work is fixed. If the work takes us longer than we estimated, that is our cost, not yours.
Changes to the agreed scope are quoted in writing, and no extra work starts until you have agreed the price.
2. Discovery delivers what it lists
An Automation Audit and a Discovery Sprint each list the outputs you will receive. If a listed output is missing, tell us within 14 days of delivery and we will put it right. If we have not supplied it within 10 working days, we refund the discovery fee. Whatever you decide, the pack is yours to keep and use with any supplier.
Limits: The refund is capped at the discovery fee you paid. It covers the listed outputs, not whether you choose to go ahead with a build.
3. Thirty days of fixes
For 30 days after a project goes live, we fix at no charge anything that does not work as the agreed scope says it should. After that, fixes are covered by a care plan or quoted.
Limits: This covers defects against the agreed scope only. It does not cover new features, design or content changes, changes of mind, or faults in third-party services and integrations outside our control. For the template website the period is 14 days.
4. You are never locked in
The accounts, the code and the data are yours. Code we write for you is yours once it is paid for, your system runs in accounts in your organisation’s name wherever possible, and if you leave you get a handover pack with the code, documentation and access.
These commitments cover work in a signed statement of work. They do not cover third-party costs such as hosting or AI usage fees, or delays while we wait for your feedback or content. Revisions are limited to the rounds stated in each package. None of this affects your rights in law.
The full terms, including limits on liability, are set out in the agreement you sign before work starts.
What you own
- The code. Bespoke work becomes yours once it is paid for in full. We keep our own general building blocks (such as sign-in and payment components) and give you a permanent licence to use them in your system.
- The accounts. Domains, hosting and databases sit in your organisation’s name wherever possible, with us as an administrator. You see every bill.
- The data. Always yours. We never use it for anything other than your project.
- The documentation. A written guide to how the system works, how to run it and how to change it.
- The way out. If you ever want someone else to look after it, you get a clean handover.
If something happens to us
Tibyan Labs is one engineer, so this is a fair question. Your system does not depend on us to keep running: it lives in accounts in your name, its code is in a repository you can access, and the documentation explains how to run and change it. Any competent developer could pick it up. If we ever have to stop looking after a system, we will give you notice and a handover.
How we use AI
We use AI tools in our work, and we think you should know exactly how.
What AI does. AI tools do much of the repeatable work: drafting code, writing automated tests, checking code for mistakes, summarising research, and drafting documents such as specifications and guides. This is part of how one senior engineer can deliver in weeks rather than months.
What a person always does. A person reviews and approves:
- every change to code before it is merged
- every release to your live system
- every message, proposal, report and document sent to you
- every price, scope and contract
- every change to your data, and any deletion of it
- the design decisions: architecture, security and how your data is handled
Nothing an AI tool produces reaches you or your live system without that review.
What never goes into an AI tool. Personal data from your live systems. We do not put it in prompts, test data, logs or monitoring. Where we need realistic data to build and test, we make up demo data.
AI in what we build for you. If your system includes an AI step (sorting emails, extracting details, drafting a reply), it is built so that a person approves the result by default. We test it on 30 real examples before launch and show you the results. We do not promise accuracy we have not measured, the running costs sit on your account or are capped in writing, and the data processing agreement names every AI provider involved.
Data protection and security
- We sign a data processing agreement with you before we handle any personal data for you.
- Each client has separate accounts, code repositories, passwords and environments.
- Access uses multi-factor sign-in, and access to your systems is removed when the work ends if you ask.
- Systems are built so that access rules are enforced by the database, not only by the screens.
- Every system we build has automated tests, and they run before each release.
- We keep personal data out of test data, logs and monitoring.
Security and data protection in full, including what we do not have yet
Working hours and support
Monday to Friday, 9am to 5pm UK time, excluding bank holidays. There is no out-of-hours or weekend cover. Support response times are written into each care plan as targets, and we report against them.
What we will not do
- Build stand-alone mobile apps for clients, or large online shops.
- Work hourly without a cap.
- Build on spec, or for equity or a share of revenue.
- Take on regulated work we are not set up for.
- Start a large build without a fixed price.
Start with a short enquiry
Tell us about the problem. Every genuine enquiry gets a reply by email within two working days. If it looks like a fit, the reply offers a short call.
Prefer email? Write to hello@tibyanlabs.com.
Printed from tibyanlabs.com/approach. Page last updated 10 November 2026.