Question 1

Who owns the code you build?

Accepted Answer

You do — fully. The GitHub repository is transferred to you with every line of code and every configuration. It's built so your team owns it from Day 6.

Question 2

What tech stack does Precode use?

Accepted Answer

Frontend: React, Next.js, responsive design, PWAs and React Native. Backend: Node.js, Python, REST and GraphQL APIs, webhooks. Data: PostgreSQL, MongoDB, Supabase and cloud storage. DevOps: Vercel, AWS and CI/CD.

Question 3

Who owns the designs you create?

Accepted Answer

You do. Design files are transferred to your account at handover.

Question 4

Do you use AI to build products?

Accepted Answer

Yes. We pair senior product designers with AI-assisted development to ship production code faster. It's senior people working with AI, not AI writing your product unsupervised.

Question 5

Does using AI mean lower quality code?

Accepted Answer

No. The output is production-ready, documented and owned by you, on the same stack we use for our own revenue-generating products. Senior people direct and review the work.

Question 6

Do I need a lawyer to work out who owns the IP?

Accepted Answer

No. Code ownership transfers to you as standard — no ambiguity, no clause to chase. Compare that to agencies where ownership is a question for your lawyer.

Question 7

Can my own developers maintain and extend the code?

Accepted Answer

Yes. It's documented, production-ready and built on a mainstream stack, with a video walkthrough so any developer can pick it up and extend it.

Question 8

Can you integrate with our existing systems?

Accepted Answer

Usually yes, via APIs. We confirm the technical approach in the pre-flight call.

Question 9

What integrations can you build?

Accepted Answer

Payments (such as Stripe), email services, authentication, calendar and scheduling, CRM systems and automation tools.

Question 10

What documentation do I get with a build?

Accepted Answer

API docs, database schemas, setup instructions, an architecture overview, and a video walkthrough of how it works and where to make changes.

Question 11

What if I want to take everything in-house after a sprint?

Accepted Answer

That's one of the standard post-sprint options: take it in-house and you own all the code and documentation, free to run it however you like.

Question 12

Can you build a Progressive Web App?

Accepted Answer

Yes — PWAs are a core part of what we build, working across iOS and Android without native app store builds.

Question 13

Is there vendor lock-in?

Accepted Answer

No. You own real, custom code on a standard stack — not a no-code platform that locks you in.

Question 14

Do you build native iOS and Android apps?

Accepted Answer

Within a V1 Sprint we build PWAs and React Native apps that run on both platforms. We don't build native Swift or Kotlin apps in a sprint.

Question 15

Do you keep a copy of or rights to my product?

Accepted Answer

The product is yours. Our own example products at precode.co/labs are separate things we built to prove the process.

Question 16

How do you handle data security in builds?

Accepted Answer

Row Level Security on all database tables, encrypted credential storage, JWT authentication and HTTPS everywhere as standard.

Question 17

Can you meet SOC 2 or HIPAA requirements?

Accepted Answer

Enterprise compliance such as SOC 2 or HIPAA is typically handled as a follow-up sprint rather than included in a first V1 Sprint. We'll be honest about what's needed in scoping.

Question 18

Will my idea be kept confidential?

Accepted Answer

We routinely work on confidential and skunkworks projects, sometimes under NDA. Raise NDA or confidentiality needs in the pre-flight call and we'll accommodate them.

Question 19

Do you sign NDAs?

Accepted Answer

Yes, we can work under NDA — just mention it early so we can put it in place before the pre-flight call.

Question 20

Where is the software hosted?

Accepted Answer

Typically on Vercel or AWS. You own the hosting accounts and the running costs (usually £30–100/month).

Question 21

Can you work in our existing codebase?

Accepted Answer

Yes — for example a 1-Day Sprint can build and deploy a small feature in an existing codebase. For larger work we'll confirm feasibility in the pre-flight call.

Question 22

What about complex, regulated, or technical products?

Accepted Answer

We specialise in making dense, technical or regulated functionality feel simple — particularly in areas like fintech and healthcare. When work is regulated, the emphasis shifts to "fast and safe."

Code, ownership & technology