Pre-launch validation
Find out if anyone wants it before you build it
We ship the landing page, or the thin version of the app, with the funnel wired from day one. In weeks you have signups, drop-off points and a go or no-go call based on numbers instead of opinions.
Six months of building, still no signal
The idea might be right. The problem is that nothing you have done so far can tell you.
The proof is at the end of the burn
You find out whether people want it after the build, when the runway is short and the sunk cost makes it hard to hear the answer.
Encouraging calls are not demand
Fifteen friendly conversations and a waitlist form with no tracking on it. Nobody can say how many people arrived, how many signed up, or where the rest went.
An engineer is off the roadmap for a maybe
Testing a new line means pulling someone off the product that already pays. The test costs a quarter of roadmap either way, whether the idea survives or not.
No agreed number for killing it
Without a target set before launch, every result gets argued. Weak numbers become "wrong audience" and the thing limps on for another two months.
From idea to an evidence-based go or no-go
Fixed scope, fixed days, agreed before anything starts. Weeks, not quarters.
We agree what would count as demand
One call to pin down who you are testing on, what they would sign up for, and the number that makes this a go. Signups from the right audience, waitlist conversion, first ten customers, whatever fits. Written down before launch so the result cannot be reinterpreted later.
We build the smallest thing that can be judged
Sometimes that is a landing page and a waitlist. Sometimes people have to touch the thing before their answer means anything, and then it is a thin app: sign in, one core action, nothing else. Next.js and Supabase when there is an app, the same static setup when there is not.
The funnel is wired before it goes live
PostHog events named per stage, forms posting into your CRM with source attached, a dashboard that shows visits, signups and first use side by side. Launch day is day one of data. Nobody has to reconstruct where the traffic came from afterwards.
You run it, read it, and decide
Traffic goes at it for a few weeks. We look at the numbers with you against the target you set: build it, change the pitch and run it again, or stop. Stopping early is a good outcome here, and it is the cheapest one on the list.
If the answer is build it, the same repo becomes the real thing. The page, the events and the CRM wiring carry over, so day one of the product already has a measured funnel behind it.
What ships
Five things, and all of them are yours
No slide deck, no research report. A live thing on your domain and the numbers coming out of it.
A landing page that makes the actual pitch
On your domain, fast, mobile handled, metadata and social cards done. Written to sell the idea properly, because a weak page tells you people did not want your copy, not that they did not want your product.
A thin app, when opinions are not enough
Next.js and Supabase: auth, one core action, and the data model behind it. Enough for someone to actually use the thing and come back, which is the only activation signal worth anything at this stage.
A funnel you can read without an analyst
PostHog events named per stage, forms into HubSpot with source and campaign attached, one dashboard: who arrived, who signed up, who used it, who came back. Set up before launch, not bolted on after.
A repo your team or your AI tooling can change
Named components, content in markdown, conventions written as files. Changing the headline for a second test is an afternoon, not a new project. If you go ahead, this is the foundation you build the real product on.
A target agreed before launch
The signup rate, waitlist conversion or return rate that makes this worth building, written down while nobody is emotionally invested in the result. It is the cheapest part of the engagement and the one that saves the quarter.
Are you going to build our product?
No. We build the thing that tells you whether to build it. That one and the rest, answered.
So where exactly does your scope stop?
At the point where you have an answer. Page, thin app, funnel, target. We are not your engineering team and we do not want to be: no roadmap, no scaling work, no multi-tenant billing. When the test says go, you build the product, and the repo we leave behind is a reasonable place to start.
Could we not just put up a landing page ourselves?
You can, and plenty of people should. What usually goes wrong is the measurement: a form with no events behind it, no source attribution, and no number agreed in advance. Then the result is a story rather than data. If you already have those three things covered, you do not need us for this.
How long does it take and what does it cost?
Weeks, and the number of days is agreed before we start. A page-only test is at the short end; a thin app with auth and a core action takes longer. You see the scope and the days after the first call, and nothing begins before you have accepted both.
What if the numbers come back bad?
Then the test worked. That is weeks spent instead of quarters, and you still have the funnel and the repo for the next idea. We will tell you honestly whether the numbers look like no demand or like a pitch problem, but we do not promise conversion rates and we will not talk you into a second round to protect the first.
We are an existing SaaS testing a new line. Same thing?
Same shape, and the point is sharper: nobody comes off your roadmap. The test lives on its own page or subdomain with its own events, so it does not muddy your existing funnel, and you can put it in front of your own users or a cold audience depending on what you need to learn.
Do you bring the traffic?
No. We do not buy ads or run outbound for you. We make sure whatever traffic you send is measured properly and lands on a page that does the idea justice. Where it comes from, your list, a launch post, a community, a small ad budget, is your call and we will help you plan it on the call.
Who owns the code and the accounts?
You do. The repo sits in your organisation, hosting, Supabase and analytics are on your accounts. If you walk away after the test, everything keeps running and any developer can pick it up.
What happens if it works?
You build the product. On the marketing side the page grows into a real site, which is the build work, and once there is traffic worth improving we work one funnel stage per sprint. Nothing obliges you to keep going; the setup runs without us.
One call, no deck
Tell us the idea, we will tell you how to test it
Thirty minutes with the person who would do the work. You leave with a view on whether a page is enough or you need a thin app, what the go number should be, and a rough scope in days. If the idea does not need us, we will say so on the call.