Skip to content

MVP Development in the UK

We are an Indian engineering team working with businesses in the UK. Written scope before any code, and a fixed quote in GBP.

Working hours

Our day runs 09:00 to 18:00 India time, which is 03:30 to 12:30 in the UK, or 04:30 to 13:30 while you are on summer time, so most of your morning overlaps with ours.

Quoted in GBP

Quotes exclude the 20% VAT in the UK, shown separately on the invoice.

Data protection

Work for this market is scoped against the UK GDPR and the Data Protection Act 2018, agreed before development starts rather than retrofitted afterwards.

Written scope

Every engagement starts with a written scope and a fixed GBP quote within 24 hours, so the price is set before work begins.

About MVP Development

One core loop, built properly, in front of real users in four to eight weeks. Auth, payments and multi-tenant data are done right from the start, so you're not rebuilding at your first hundred customers. We ship our own products too, so we know which corners are safe to cut.

What the engagement includes

  • A one-page scope that names the core loop and, just as important, what's left out of version one
  • A stack chosen for the next two years, not the next demo: usually Next.js, a Node.js or Laravel API, and PostgreSQL
  • Auth, roles and per-customer data isolation built in from the first commit
  • Payments working end to end, including failed payments and refunds
  • Analytics on the core loop, so you can see whether people actually use the thing
  • Full code ownership in your GitHub from day one, and documentation a future hire can pick up
  • The same senior engineers from scope to launch, not a sales team followed by juniors

Send the scope and you get a written scope and a fixed GBP quote back within 24 hours.

Get a quote in GBP

R&D relief, an SEIS round and who owns the code: the UK founder's side of an MVP

For a UK founder the first effect of building an MVP offshore lands on the tax plan rather than the code. Most MVPs are not R&D in the tax sense at all: HMRC's test is whether the project seeks an advance in science or technology by resolving an uncertainty that an expert could not resolve from available knowledge, and assembling an app from established methods rarely does. Where some of the work does qualify, Finance Act 2024 narrowed it for accounting periods beginning on or after 1 April 2024. Under both the merged expenditure credit and the enhanced support for loss-making R&D intensive SMEs, a payment to a contractor counts only if the R&D is done in the UK, or done abroad because conditions it needs are absent here, present where the work happens, and wholly unreasonable to replicate in the UK. HMRC's guidance names the two conditions that can never justify overseas work, the cost of the R&D and the availability of workers, and calls that list exhaustive. A cheaper team, or engineers the UK market cannot supply this quarter, is exactly what the rule excludes, so a model counting on a credit against our invoices is counting on money that will probably not arrive. What can still qualify is work that happens here, such as the time your own UK staff spend resolving the uncertainty, since the overseas restriction reaches contractor and agency worker payments only. The merged scheme also gives the claim to the company that decided the R&D was needed, so the record of what was uncertain should be written and kept by you. The paperwork has fixed dates: a first claim needs a claim notification within six months of the end of the period of account, and the additional information form must reach HMRC before the Company Tax Return or the claim is rejected. Whether any MVP spend qualifies is for your accountant, ideally before the statement of work is signed.

The SEIS round that often pays for the build has its own clock, and the build sits right in the middle of it. A company can raise up to £250,000 under the Seed Enterprise Investment Scheme if, when the shares are issued, it has gross assets of no more than £350,000, fewer than 25 full-time equivalent employees, and a trade carried on for no more than three years. The money must be spent within three years on the qualifying trade, on preparing to carry it out, or on R&D expected to lead to it, and an MVP is usually the largest single line in that spending. That gives our invoices a second job as evidence. The compliance statement, form SEIS1, can only be submitted once the company has traded for at least four months or spent at least 70 per cent of the amount raised, and investors cannot claim relief until HMRC accepts it and issues the SEIS3 certificates. Milestone invoices tied to delivered features, dated and described in the same terms as the business plan, make that 70 per cent straightforward to show. The risk to capital condition is where an outsourced build needs a sentence of explanation. HMRC says it looks at a company's use of subcontractors, among other things, and expects an intention to grow and develop the trade over the long term. An MVP built by an agency sits comfortably with that when the plan shows the company owning the product, the roadmap and the customer relationship, with a route to its own team, rather than a structure in which the supplier effectively is the business. Advance assurance lets you ask HMRC beforehand whether the share issue is likely to qualify, and the application asks for spending broken down by activity, which is the breakdown our proposal already gives. Which scheme fits your round, and whether your trade qualifies, is for your accountant.

The last check is ownership, because an investor's solicitor will ask about it in due diligence and it cannot be fixed cheaply after a falling out. The Intellectual Property Office's guidance is plain that when you commission someone to create a copyright work, the first owner is the person or organisation that created it, not the commissioner, unless you agree otherwise in writing. Where the contract is silent a court may find only an implied licence to use the work for the purpose it was commissioned, which falls well short of owning it. Source code is a copyright work, so that default runs against the founder unless the contract says otherwise. So the agreement should assign the copyright in the code, designs and documentation written for you, in writing, list the open source packages separately because those stay under their own licences, and keep the repository in your organisation's account from the first commit rather than handing it over at the end. The product's name deserves the same care before the launch page goes live. Companies House guidance warns that a company name too similar to another company's name or trade mark may have to change if someone complains, so an accepted company name is not clearance. Since 1 January 2021 an EU trade mark has not protected a brand in the UK, so a founder who filed only at the EU office has nothing here. A UK application is checked against existing marks and published so that others can oppose it, and the IPO says grant usually takes three to four months, which argues for filing when the name is chosen rather than when the app store listing is ready. A founder with no UK address also needs an address for service in the UK, Gibraltar or the Channel Islands to file at all. How the assignment is worded and which classes to file in are for your own counsel.

How we work with UK clients

UK engagements tend to start with procurement questions rather than technical ones. Who holds the data, which law governs the contract, whether you can produce a record of processing if the ICO asks. We answer those in the proposal instead of leaving them to a legal review three weeks in, because that review is where UK projects usually stall.

Invoicing is the other thing worth settling early. We are outside the UK, so services we supply generally fall under the reverse charge and your finance team accounts for the VAT rather than paying it to us. Our invoices say so explicitly. We quote in pounds, the figure does not move with the exchange rate mid-project, and payment by bank transfer avoids the card fees that make a five-figure invoice unnecessarily expensive.

Send the scope and you get a written scope and a fixed GBP quote back within 24 hours.

Get a quote in GBP

Full service detail

This page covers how we work with clients in your market. The complete MVP Development page, with the full technical detail, process and frequently asked questions, is written in English.

Read the full service page (English)

Questions UK clients ask

How does VAT work if you are based in India?

For most business-to-business services supplied from outside the UK, the reverse charge applies: you account for the VAT in your own return rather than paying it to us, and it is typically neutral if you are fully recoverable. Our invoices state the position clearly so your accountant is not guessing. If your situation is unusual, for example partial exemption, we would rather your accountant confirms the treatment before we invoice than after.

Are you compliant with UK GDPR and the Data Protection Act 2018?

We build to it rather than claiming a certificate. In practice that means data minimisation designed in rather than bolted on, a documented lawful basis for each processing activity, retention periods that actually delete, subject access and erasure handled as features rather than manual database work, and hosting in a region you approve. Where we process personal data on your behalf we sign a processor agreement setting out exactly that.

We are a public sector body. Can you meet the accessibility regulations?

Yes, and it is scoped from the start because retrofitting accessibility is considerably more expensive than building it in. We work to WCAG 2.2 AA, test with a screen reader rather than relying on an automated scan, and produce the accessibility statement the regulations require. Automated tools catch perhaps a third of real issues, which is why the manual pass is not optional.

Which law governs the contract, and what about IR35?

We are happy to contract under English law with the courts of England and Wales, and most UK clients prefer that. IR35 does not apply to us: it governs individuals working through an intermediary, and you are engaging a company for a defined deliverable rather than a person for their time. Your accountant will want to see that the contract reflects that, and ours does.

MVP Development: common questions

How much does MVP development cost?

From £630for the smallest SaaS MVP with one core flow, £1,300 to £3,600 for a typical lean MVP, £3,600 to £8,000 for a standard one, and £8,000 and up for complex or funded products. The biggest cost driver is scope, which is why we spend real time cutting it before we quote.

How long does it take to build an MVP?

Four to eight weeks for a lean MVP with one core loop. Eight to sixteen weeks for a standard MVP with more integrations. If a quote promises a full product in two weeks, ask what they're leaving out.

Do I own the code?

Yes, fully, from the first commit. The code lives in your GitHub organisation, the hosting is in your account, and there's nothing we hold back. If you hire your own team later, they take over without asking our permission.

Web app or mobile app for my MVP?

Usually a web app first. It's faster to build, easier to change weekly, and works on phones anyway. Build the native app once you know people use the product and what they use it for. The exception is products that truly need the phone, like location tracking or offline use.

Do you work with non-technical founders?

Most of our MVP clients are non-technical founders. We explain trade-offs in plain language, show working software every week, and write the documentation your first technical hire will need.

Send the scope and you get a written scope and a fixed GBP quote back within 24 hours.

Get a quote in GBP

Other markets we work in

Working with the UK

Tell us what you are building in the UK

Send the scope, or just the problem. You get a written scope and a fixed GBP quote back within 24 hours, from the engineers who would do the work.