TreeInAPool
Work

Proof, not portfolio filler.

Every case study follows the same template: the problem, what we did about it, and the numbers after launch. Each one says plainly whether it was built for a client or is our own product, because a portfolio that blurs the two is not evidence of anything. Where a figure has not been confirmed, none is shown.

Frequently asked


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.

About two hours a week: one demo, plus decisions when a question is genuinely yours to answer. Everything else is our job.

Often, yes. It starts with an audit of what exists so nobody promises a timeline before reading the code.

Have a process that looks like this?

Book a free discovery call