concept.zone

How we work.

Two jobs, one team. First we get your product to market — workshop, customer analysis, prototypes every 48 hours, a real build, a launch on day 28. Then we keep it running and getting better, every week, for as long as you want.

Building something new ↓ Running it ↓
A product team working through a design workshop around a table
Workshop on day 1 A prototype every 48 hours Live URL in week 1 A release every Friday Launch on day 28

Building something new.

Most failed products were built well and aimed wrong. So the first ten days are about aiming: who buys this, what they will pay for, and what the smallest version is that earns money. The building comes after, and goes fast because nobody is guessing.

  1. 00

    A 30-minute call

    Before we start

    You tell us what should exist and who it is for. We tell you whether it fits four weeks, what it will cost, and when we can start — or that we are not the right team for it.

    You leave with a fixed price and a start date. Not sure yet? The €490 Blueprint is this step done properly: a 90-minute working session and a written build plan you can take anywhere.

  2. 01

    Design workshop

    Day 1 · half a day

    A working session with you and anyone who knows the customer. We map who the product is for, the one job it does for them, the screens that job needs, and — just as important — everything that waits until after launch. We sketch the core flow together on the call.

    You get a one-page product brief, a flow map of the core journey, and a written list of what is in and out of version one.

  3. 02

    Customer analysis

    Days 2–4

    Five to eight conversations with people from your target market — from your network or a list we build together — about how they solve the problem today and what they pay for it. Alongside: the competitors they mention, what those charge, and how many people search for the problem.

    You get a short findings note: what customers said in their own words, what they would pay, who you are really up against, and the scope change it implies — before a line of production code exists.

  4. 03

    Prototype loops

    Days 3–10 · every 48 hours

    A clickable prototype of the core flow within 48 hours of the workshop. It goes in front of real users the same day; what confuses them changes before the next version, 48 hours later. Three or four loops in, the flow is settled and the interface design is done.

    You get a prototype link you can share with anyone, and notes from every test round.

  5. 04

    Build

    Weeks 2–4

    The real product, on a live staging URL from the first week, so you click through it instead of reading status updates. Every Friday is a demo of what shipped and a decision on what comes next. Sign-in, payments, email, analytics and search indexing are part of the build, not extras.

    You get working software every week, and a say in every week's priorities.

  6. 05

    Launch

    Day 28

    Go-live on your own domain and accounts: hosting, database, payments, email sending, analytics and search console are in your name from the start. We check the live site end to end — home, sign-up, checkout — before we call it launched.

    You get a live product you own completely, 30 days of fixes, and the option to have us run it from here.

A team testing a prototype together on laptops

Why 48 hours, and not two weeks.

The expensive mistakes in a new product are decided in the first ten days. Short loops make them cheap.

Two-week sprintsA wrong assumption survives for two weeks of building before anyone sees it on a screen.Slow to correct
Big spec firstWeeks of documents describing a product nobody has clicked. The first real feedback arrives at launch.Late feedback
48-hour loopsA user clicks the idea on day 3. By day 10 four versions have been tried, and the build starts on a flow that already works.Cheap to change

Running it, every day after.

Launch is when a product starts needing someone. Run is that someone: the same senior team, with operations tooling that watches every product we look after. It starts with a takeover — for a product we built, or for one someone else did.

  1. 01

    Takeover

    Weeks 1–2

    We get access to everything — code, hosting, domain, database, payments, email — and make sure it is in your name. Backups are taken and a restore is tested. We read the codebase, write down how it works, and fix whatever is broken first. Then monitoring, error tracking and a deploy pipeline with a live check after every release go in.

    You get a takeover report: what we found, what we fixed, what is risky, and the first improvements we recommend.

  2. 02

    Every week

    From week 3
    MondayYou pick this week's improvement from the list, or bring a new one.
    Tue–ThuWe build it, alongside fixes for anything the monitoring caught.
    ThursdayRelease, then a check of the live site: home, sign-in, checkout.
    FridayA short note: what shipped, what broke, what is next.
  3. 03

    Every month

    The report

    Uptime, incidents and how they were handled, security updates applied, everything shipped, the numbers that matter for your product — visitors, sign-ups, payments — and our recommendation for the month ahead.

A normal day on a product we run.

None of this needs a ticket from you.

Uptime and checkout probeOK
Dependency and security scan0 critical
Two new errors reproduced and fixedDeployed
Live check after deploy — home, sign-in, checkoutOK
Support inbox — four replies drafted in your voiceFor review
This week's improvement: invoice PDFsShips Thursday
Backups verified, restore test passedOK
Two engineers reviewing a product's monitoring together

When it should grow faster.

Grow is Run plus a product team's worth of work aimed at growth: unlimited requests, shipped one at a time, and a weekly call to decide what moves the numbers.

Experiments

Pricing, onboarding and sign-up changes tested against real traffic, kept only when the numbers say so.

Search and AI answers

Pages and guides written for the questions your customers type into Google and ask ChatGPT.

Lifecycle email

Onboarding, activation and win-back messages that go to the right person at the right moment.

Customer conversations

Regular calls with users and churned users, so the roadmap follows evidence rather than opinions.

Analytics you trust

A funnel from first visit to paid, measured the same way every week.

Weekly releases

Every week something visible ships, verified on the live site.

What never changes.

You own everything

Code, data and every account are in your name from day one. Leave whenever you like and take it all with you.

Senior people only

No account managers, no juniors, no hand-offs. You talk to the people who build and run it.

Live from week one

You click a real URL, not a status report. Every Friday there is something new to click.

Measured from day one

Analytics and search indexing are in place at launch, so every later decision has numbers behind it.

Fixed prices

Build is a fixed price. Run and Grow are flat monthly fees you can pause or cancel any month.

Checked, not assumed

Every release is verified on the live site — sign-in and checkout included — or rolled back.

Where to start.

An idea, nothing builtBlueprint, then Build. The workshop and a written plan for €490, credited in full when the four-week build starts at €6,900.Prices
Built, but nobody looks after itRun, from €1,900 a month. The takeover is included; weekly improvements start in week three.Prices
Live with users, growth stalledGrow, €4,900 a month. Everything in Run, plus experiments, content, lifecycle email and a weekly call.Prices

Tell us what should exist.

Thirty minutes. You leave with a fixed price and a start date. Build €6,900 once, then Run from €1,900 a month — or a straight answer that we're not the right fit.

Book a 30-minute call Or write to contact@concept.zone