A small team, on purpose.
Every build has one person who scopes it, one person accountable for it, and the right hands building it. Here is honestly how that works.
Rishi Gupta · Founder and AI consultant
Fifteen years in mechanical engineering in the UK, in engineering management and automation, including Amazon Robotics and Jaguar Land Rover, with nearly a decade in the car industry. A master's in motorsport engineering from Coventry University. After engineering, consulting: now business, AI, automation and software.
Rishi scopes every build himself, runs every discovery interview, and is the person on every call. The engineering habit carries over: measure the process before changing it, validate each stage before building on it.
How delivery actually works
25 Tera Watts is founder-led, working with a small network of vetted partner developers. Every developer signs a non-disclosure agreement and a master services agreement before touching client work, and builds are specified and reviewed by Rishi, not handed off. You always know who is accountable: the same person who scoped the work.
What happens after a project ends
- You own everything. The code, the data and the infrastructure accounts end a build in your name, not ours. There is nothing we could hold over you.
- Four weeks of free fixes. Every proposal carries four weeks of bug fixes and minor adjustments after go-live as standard, unless the document says otherwise.
- Support if you want it, no lock-in. Where a client asks for ongoing support, it runs on a monthly plan they can leave. Several do; none are obliged to.
The honest version of the question behind this page (what happens if something happens to a one-person company?) is answered straight, in writing, on the blog.