TreeInAPool

We turn prototypesinto productspeople pay for.

TreeInAPool is a product development agency. Bring us a no-code prototype, a spreadsheet, or a sketch on a whiteboard. We ship the production version, designed and built to be maintained.

Proof you can open

A payments product in both app stores, taking real money from real users

Vuvu.ng shipped in November 2024 and has been running since. Every claim on this site links to the thing itself, and no figure goes up until the client has confirmed it. See the work.

You are hiring the person who scopes the work, runs the sprints and hands it over at the end. No account manager in between, and nobody touches your project who was not briefed by the founder directly.

01 · What we build


Your Lovable or Bubble build, rewritten as a product that survives real users and real load.

4–8 weeksYou own: Code + accounts
Learn more →

Flows, screens and a component system your developers build from directly, with the states and edge cases drawn, not left to interpretation.

2–4 weeksYou own: Files + tokens
Learn more →

Discovery through launch for one product: a web app, a mobile app, or the internal portal your operation currently runs on spreadsheets.

8–14 weeksYou own: The whole product
Learn more →

The steps someone on your team does by hand every day, such as quoting, triage, reconciliation and reporting, moved into software, with a human still in the loop where it matters.

3–6 weeksYou own: Pipelines + evals
Learn more →

02 · Why TreeInAPool


Four sprints stacked in sequence, each one ending at a live URLSPRINTDEMOS1S2S3S4EVERY ROW ENDS AT A URL YOU CAN OPEN

You are never guessing what happened this week

Most agency relationships go quiet between invoices. Ours can't: every sprint ends with a live URL you can open, click, and break. If a week went badly, you find out in that demo, not in a post-mortem.

  • Two-week sprints, each ending in working software
  • A re-published roadmap showing what shipped and what slipped
  • One person accountable, reachable, and in the demo
A signed scope beside the only route a change is allowed to take: quoted, approved, builtWRITTEN SCOPEANY CHANGEQUOTEDAPPROVEDBUILT

The scope is a document, not a conversation

Discovery ends with a written scope: what's included, what isn't, what it costs, and when it lands. Changes are priced in writing before anyone builds them, so the number you approved is the number you pay.

  • Fixed scope and price agreed before a line of product code
  • Change requests quoted, then approved, then built
  • No line item you can't trace to something you asked for
Repository, hosting, analytics and domain crossing from us to you at launchUSYOULAUNCHREPOSITORYTRANSFERREDHOSTINGTRANSFERREDANALYTICSTRANSFERREDDOMAINTRANSFERRED

You keep everything when we're done

Repositories, hosting, analytics, and domains transfer to you at launch. If you never speak to us again, the product keeps running and any competent developer can pick it up.

  • Code and accounts transferred, not licensed back
  • Documented architecture a new team can read
  • 30 days of post-launch support, retainer optional after

04 · How an engagement runs


01

Discover

One call, one written scope. You leave knowing price and timeline. 1 week.

02

Design

Flows and screens you approve before a line of product code is written. 2 weeks.

03

Build

Weekly demo on a live URL. You test what exists, not a status report. 4–10 weeks.

04

Launch

Deploy, hand over the code and the accounts, then 30 days of support.

Read the full process, stage by stage →

05 · The roadmap you get on day one


Sprint plan, worked example · full-cycle build7 sprints · 14 weeks
WorkstreamS0S1S2S3S4S5S6
Discovery
Design
Build
QA & hardening
Launch & support

Illustrative plan. Yours is written during discovery, with dates, and it is the document we are both held to.

No black box

Two-week sprints, each ending in something you can open and click. The roadmap is agreed before we start and re-published every sprint, so you always know what shipped, what slipped, and what is next.

Sprint length2 weeks
Demo cadenceEvery sprint
Scope changesPriced, in writing

06 · Questions we get asked


Fixed scope, fixed price, agreed in writing after the discovery call. If scope changes mid-project, the change is priced and approved before we build it. No surprise invoices.

You do. Repositories and accounts are transferred to you at launch, not licensed back to you.

A weekly demo on a live URL, plus an async channel for day-to-day questions. No status-report theatre. You see the actual product every sprint.

30 days of support are included with every full build. After that, a maintenance retainer is optional. Nothing is forced.

That's what the discovery call is for. You'll leave with a written recommendation, including "you don't need us yet" when that's the honest answer.

07 · Book the call

Thirty minutes, and you leave with a scope

Bring whatever you have. We will tell you what it takes to ship it, what it costs, and whether we are the right people to build it.

Tell us what you're building