Co-Founder Programme We co-found three products a year for 10 to 15 per cent equity. Next cycle: January 2027. Next cycle Jan 2027 Booking projects for Q1 2027
For UK start-ups

Build version one with code your investors will want to see.

The median advertised salary for a UK software engineer is £70,000, or £100,000 in London (ITJobsWatch, October 2026), before employer National Insurance at 15 per cent. Most founders cannot hire a team before they raise. We give you a senior team now, with everything set up the way investors' lawyers expect to find it.

  • Free 30-minute call
  • Fixed quote in writing
  • Code you own
Where you are now

Help that fits your stage.

01
Idea
Test it before you build it.
A short discovery phase to pin down the problem, the users and the smallest version worth building, with a written scope and a fixed quote.
Read more
02
Pre-seed
An MVP or a fundraising prototype.
A working product, not a slide deck: real sign-in, the core workflow and the data investors want to see, in about 90 days for a well-scoped MVP.
Read more
03
Seed
Scale it and hire your team.
More capacity when the roadmap grows, a fractional CTO to make the big technical calls and help hiring your first engineers.
Read more
04
Series A
Ready for technical due diligence.
Documentation, IP paperwork, licence checks and a clean handover, so an in-house team can take over without rewriting what you have.
Read more
Free 30-minute call

Got an idea and no technical co-founder? Talk to an engineer.

Thirty minutes with a senior engineer, free and with no obligation. Bring the problem, not a brief.

Ownership

You own everything, and the paperwork proves it.

Under UK law, the copyright in work commissioned from a contractor belongs to its author unless it is assigned to you in writing (GOV.UK, Intellectual Property Office). Paying for the code is not enough on its own, and investors' lawyers will ask to see the assignments.

01 A written IP assignment Our contract assigns the copyright and other IP in everything we build for you to your company, in writing, as section 90 of the Copyright, Designs and Patents Act 1988 requires.
02 Your repository from the first commit Code lives in your company's GitHub or GitLab organisation from day one, and you hold the admin access.
03 Your accounts and domains Cloud hosting, app store, analytics and domain accounts are registered to your company, not to us.
04 An open-source licence register A list of every open-source component and its licence, so copyleft surprises do not turn up in due diligence.
05 No lock-in at any point Documentation and handover notes at every milestone, so another team, or your first hire, can pick up the work.

Sources: GOV.UK, Ownership of copyright works; Copyright, Designs and Patents Act 1988, section 90. General information, not legal advice.

Due diligence

Investor-ready by default.

Investors' lawyers check IP assignments from founders, employees and contractors, data processing agreements, and the records behind any R&D claim (Ashfords, founder due diligence checklist). We build so those answers already exist.

01
Architecture notes
How the system fits together, where the data lives and why each choice was made, in plain English.
02
Tests and code review
Automated tests where they earn their keep, and every change reviewed by a second senior engineer.
03
Security basics
Multi-factor authentication, least-privilege access, dependency scanning and secrets kept out of code.
04
Data protection records
A Data Processing Addendum, a data map and the privacy documentation UK GDPR expects.
05
A due diligence pack
IP assignments, the licence register, architecture notes and access lists, gathered in one place before you raise.
06
Handover documentation
Set-up guides and runbooks, so your first in-house engineer is productive in days, not months.
Week to week

How working with us actually feels.

01
Demo
A working demo, every week.
Something real on a staging site you can click through every week, not a status report.
02
Channel
A shared channel, your choice.
Slack, Microsoft Teams, email or a call. You talk to the engineers doing the work, in UK hours.
03
Board
A board you can open.
Every task on a shared board in Jira, Linear or GitHub, so you can see progress at any time.
04
Lead
A named senior lead.
One senior engineer who owns your product, joins every call and stays from discovery to launch.
Paying for the build

Two ways to pay.

Cash, on milestones

A fixed quote, paid as it ships.

After discovery you get a fixed, itemised quote in pounds and a milestone plan. You pay as each stage is shown working, and any change of scope is costed in writing before we build it. Nothing is paid in full up front.

How discovery works
Equity, three times a year

The Co-Founder Programme.

For a few founders a year, we carry 50 to 70 per cent of the build cost as services in exchange for 10 to 15 per cent equity in ordinary shares. You bring a UK limited company, the idea, the rest of the build cost and a marketing budget of at least half the build cost. The next cycle starts in January 2027.

Read the programme and term sheet
Founders ask

Frequently asked questions.

Who owns the code you build for our start-up?

Your company does, once the work is paid for. Our contract assigns the copyright and other intellectual property to your company in writing, which UK law requires for an assignment to work. The code lives in your repository from the first commit, and your company holds the cloud, app store and domain accounts.

Will investors accept code built by an agency?

Investors care less about who wrote the code than whether you own it, whether it is documented and whether it can scale. We give you written IP assignments, a licence register, architecture notes and tests, so a technical due diligence review finds a product, not a problem.

What happens if we stop working together?

You keep everything we have built and you have paid for: the code in your repository, the accounts in your name and the documentation. We hand over cleanly, with notes your next developer or first hire can follow, so the product keeps moving.

How long does an MVP take?

About 90 days from kick-off to a launchable MVP for a well-scoped product, with a working demo every week. A fundraising prototype can be quicker. Discovery comes first and sets the exact scope and timeline in a fixed quote.

Can we claim R&D tax relief on what we pay you?

Possibly, for parts that are genuinely R&D, and the claim would be yours, not ours. Since April 2024 the rules limit it to 65 per cent of the qualifying part of an unconnected supplier's fee and generally exclude work done outside the UK. Ask your adviser, and ask any supplier, including us, where the work will be done.

Does the Co-Founder Programme affect our SEIS or EIS round?

Our shares get no relief, because they are not paid for in cash. We structure the programme so we never control the company and most of any SEIS or EIS money is not paid to us, but HMRC decides eligibility. Apply for advance assurance with independent advice.

Can you be our CTO until we hire one?

Yes. Our fractional CTO service gives you a senior technical lead a few days a month for the roadmap, architecture, supplier decisions, investor due diligence and hiring your first engineers. When you are ready to hire a full-time CTO, we help you find them.

Do you sign an NDA before we share our idea?

Yes, a mutual NDA before any detailed session. For a first conversation, describe the problem and the market rather than the secret parts. Our standard terms also include confidentiality, and anything you share stays inside the team working with you.

Still have a question? Ring 07723 431000 and speak to an engineer.

Bring the idea. Leave with a plan you can take to investors.

Thirty minutes with a senior engineer, free and with no obligation.

Or ring us07723 431000

What happens next

  1. A free 30-minute callWith a senior engineer, at a time that suits you. No obligation.
  2. A short discoveryWhat it covers is agreed in writing before it starts.
  3. A written scope and a fixed quoteIn pounds, before you commit to a build.

A senior engineer replies within one working day, in UK hours.

Cookie preferences

Choose which cookies we may use. You can change this at any time using the Cookie settings link at the bottom of every page.

Strictly necessary Always on

Keep the site secure and working, and remember this choice.

Count visits and show which pages are useful, so we can improve the site. Google Analytics.

Measure our advertising and show relevant ads on other sites. Google Ads, Meta and LinkedIn.

Cookie Policy · Privacy Policy