Campaign: Product Builder (*dev)
Back to all campaigns.
Status: started September 2026. productbuilder.dev, prototypeinaday.dev and mvpinaweek.dev are live. Since 23 October 2026, *dev is the focus campaign; paid Shit* ads are paused.
Internal name: *dev, for the three .dev sites together. The name is internal only: it does not appear in headlines on the sites.
Target audience: startups, not corporates (decided in the Strategy & Growth meeting of 24 September 2026). Sales area: the EU only, for now. Google Ads target the Netherlands only.
Contact address: info@productbuilder.dev on all three sites (receiving since 2 October 2026). Phone numbers are on Contact.
Language: English on all *dev sites. No Dutch on these sites (decided on 2 October 2026). The Google Ads are Dutch, with Dutch keywords; one ad line says the site is in English.
Websites
| Site | Role | Hook | Status |
|---|---|---|---|
productbuilder.dev |
Hub and education: what a Product Builder is; links to both offers | “What is a product builder?” | Live |
prototypeinaday.dev |
Offer: 8 hours of total effort, including preparation and handover. Landing site of the Google Ads | “1 day. Something to point at.” | Live since 2 October 2026 |
mvpinaweek.dev |
Offer: one working week of 40 hours of effort, including preparation and handover | “1 week. A working MVP.” | Live |
prototypeineendag.nl and mvpineenweek.nl stay registered and will redirect (301) to the .dev sites.
Offer
Timeboxed by design. Both offers have a fixed effort budget and flexible scope. We build what fits, in priority order; what does not fit goes to the top of the backlog. Every offer ends with a demo and handover, never with “almost done”. Preparation and handover are part of the effort budget of both offers. Current since 23 October 2026.
| Offer | Preparation | Build | Demo and handover | Total effort | Scope decision | Price (excl. VAT) |
|---|---|---|---|---|---|---|
| Intake | — | — | — | Free, up to 1 hour | — | €0 |
| Prototype in a day | 1 hour | 5.5 hours | 1.5 hours | 8 hours | hour 5 | EUR 1,199 |
| MVP in a week | 2 hours | 34 hours | 4 hours | 40 hours | hour 26 | EUR 5,999 |
- Prototype: one clickable core flow with mock data, a walkthrough, the repository, and a short note with next steps. No working demo with real data, no integrations, no login. We do not promise a live link.
- MVP: one agreed user journey that really works, with a database, standard login and deployment on Cloudflare, plus a walkthrough, the repository and a prioritised backlog. Not included: payments, multiple user roles, external integrations and hosting on the customer’s own servers; those need a custom proposal.
- Prototype first (internal rule). An MVP is only sold after a prototype. The sites do not explain this rule; existing lines such as “Don’t have a prototype yet?” may suggest the order. A customer who brings their own prototype still needs us to learn the domain; quote extra hours for that.
- No crediting. The prototype price is not deducted from the MVP price.
- Prices are fixed per package and value-based (about €150 per hour). Both sites write the price in English notation (EUR 1,199); Dutch material writes €1.199.
- A “day” and a “week” describe effort, not guaranteed elapsed calendar time. Agree the calendar delivery date separately, based on scope, availability, access and feedback. These are timeboxes, not fixed-scope delivery promises.
- Assess during intake whether the core outcome and acceptance criteria fit the package effort. End each package with a demo and handover; lower-priority work goes onto the backlog with a separate quote. Projects that exceed the package scope receive a custom proposal before commitment.
- Hours are logged in the repository, one line per block (date, hours, who, what). The customer gets a short status every working day.
- Waiting time caused by the customer does not count towards the box.
- Hosting: we build on our own stack (Cloudflare, GitLab) and hand the repository over at delivery. Hosting at the customer costs extra hours.
- Build the prototype on the stack of the MVP, so that the MVP continues in the same repository.
There is no finished startup project with real numbers yet. Graphic iDraw Rescue was built in 40 hours (campaign page) and serves as the first example of what 40 hours delivers.
Do not put “factor 10” in the headline. Show the evidence first, then the claim: “up to a factor 10 on the first working version”, never “10x cheaper”.
Where the offer is published: the three *dev sites (pages, JSON-LD, FAQ schema, llms.txt), the Product Builder flyer (product-builder/product-builder-flyer-en.typ in tcfbv/sales/services, copied into the three .dev repositories), the rates PDFs on conveniencefactory.com (rates-and-service.typ and tarieven-en-services.typ in tcfbv/sales/services), the cost answer on conveniencefactory.com and shitwemoetenietsmetai.nl. Change all of them together. The site tests reject the old offer, including in the PDFs.
History: until 23 October 2026 the prototype was 24 hours for EUR 2,399 and the MVP seven build days of 24 hours (about 180 hours) for EUR 16,799.
Package strategy
| Package | Customer question | Outcome | Price (excl. VAT) |
|---|---|---|---|
| Prototype in a day | “Is this idea worth building?” | One clickable core flow with mock data that makes the idea tangible, with a short note on next steps | EUR 1,199 |
| MVP in a week | “Can first users start using this?” | One user journey that really works, with deployment and handover | EUR 5,999 |
- Lead with a meaningful step at a predictable price. Agree the core outcome, boundaries, and acceptance criteria before commitment. The effort breakdown supports planning; it does not set the value of the package by itself.
- For the MVP, define the frontend, backend, database, standard login, deployment, and handover around the agreed user journey. The scope page on
mvpinaweek.devshows three single-role examples. Decide package suitability during intake. - Larger or more complex projects receive a custom proposal. Start without additional MVP tiers. Introduce further packages only when customer conversations and completed projects show recurring differences in scope, effort, and value, such as payments, multiple user roles, or external integrations.
- Review price and scope after the first eight weeks of the Google Ads test (see Channels).
Way of working and client communication
This working model applies to both prototypeinaday.dev and mvpinaweek.dev. Explain it during intake and include the agreed arrangements in the proposal and kickoff notes.
Our tools and delivery environment
- We use our own tools and established workflow. Jira is the shared reference for agreed scope, priorities, work in progress, blockers, and the remaining backlog. GitLab holds the code, version history, and effort log; Cloudflare is our default deployment and hosting stack.
- Keep the workflow lightweight: a clear Jira board, one repository, and a demo environment appropriate to the package. Record scope decisions and feedback in Jira so they remain connected to the work.
- Agree how the client follows progress at kickoff: direct board access where practical, or concise updates with relevant board items and demos. Confirm access arrangements before promising them.
- Work in the client’s tools, deployment into their infrastructure, or additional reporting requirements must be agreed and scoped before starting. Customer hosting requires additional effort; price it separately if it falls outside the agreed package.
What to agree with the client before starting
- Outcome: the question the prototype should answer, or the core task first MVP users should be able to complete. Agree acceptance criteria, priorities, and what is outside the package.
- Timing: the package describes effort. Agree the calendar delivery date separately, including availability and feedback moments.
- Client contact: one person who can prioritise, give feedback, and approve scope decisions. Agree a communication channel and expected response times.
- Inputs: access to required systems, test accounts, API credentials, sample data, content, and brand assets. Identify dependencies before scheduling work and agree a suitable secure channel for credentials.
- Tools and hosting: explain our Jira/GitLab/Cloudflare workflow, how progress will be visible, and any external services or recurring hosting costs. Agree who owns the relevant accounts and pays these costs.
- Handover: agree repository ownership/access, deployment destination, documentation, and who will operate the result after delivery. Make clear what follow-up support or further development requires a separate agreement.
During the work
- Send a short status every working day: what was completed, what comes next, and any blocker or decision needed. Use a demo or preview when there is something useful to show.
- Ask the client to return consolidated feedback through the agreed contact and channel. Record actionable feedback on the Jira board and prioritise it against the agreed outcome.
- Review scope at the package checkpoints: hour 5 for the prototype and hour 26 for the MVP. Agree priority changes within the effort budget; put work that does not fit in the follow-up backlog.
- Client waiting time does not consume the effort budget, but can move the calendar delivery date. Communicate schedule changes as soon as a dependency or delayed decision affects delivery.
Handover
Demonstrate the agreed result, hand over the repository and agreed deployment/access details, and walk through how to run or use it. Include relevant setup notes, known limitations, and the prioritised next steps. Agree how the client receives the remaining Jira backlog; do not assume they will keep using our tools. Preparation and handover are part of each package’s effort budget above.
Suggested client wording
We work with our own tools: Jira for scope and progress, GitLab for the code, and Cloudflare as our default hosting platform. Before starting, we agree the core outcome, delivery date, access requirements, and feedback moments. You receive a short update every working day and demos as the work takes shape. At delivery, we walk you through the result and hand over the repository, agreed deployment details, and next steps. If you need us to work in your tools or infrastructure, we agree that upfront.
Positioning
Definition we promote: a Product Builder is a senior product professional who uses AI to turn a business problem into a working digital product, end to end. One person covers the roles of Product Owner, Product Manager, Business Analyst, UX researcher and designer, architect, front-end, back-end and full-stack developer, QA, DevOps, cloud, data and security engineer, and technical writer.
Core line: “AI can move fast in any direction. Experience makes sure it is the right one.”
Campaign tagline (proposal): “Hours, not quarters.”
The two messages
The campaign has to land two things:
- The term. People do not know “Product Builder” yet, and often assume it means Product Owner.
- The offer. Because one senior Product Builder with AI replaces a whole team, a quote can come out almost a factor 10 lower than a traditional project. Prospects do not believe this yet. Making this claim credible is the main challenge of the campaign.
Site structure
- mvpinaweek.dev: headline “1 week. A working MVP.”; explains one working week of 40 hours of effort, including preparation and handover, with calendar delivery agreed separately. CTA: “Discuss your MVP”. The scope page is
/what-fits-in-a-one-week-mvp/; the old/what-fits-in-a-seven-day-mvp/redirects (301) to it. - prototypeinaday.dev: headline “1 day. Something to point at.”; explains the 8-hour effort (1 hour preparation, 5.5 hours build, 1.5 hours demo and handover) with a scope decision at hour 5. CTA: “Discuss your prototype”. Links on to
mvpinaweek.dev. - productbuilder.dev: the header link is “Work with one”; the cost page lists both packages.
The site copy itself lives in the site repositories in tcfbv/brand (umbrella/<site>/).
Visual identity
The three sites form one family with productbuilder.dev: Archivo Black for headlines, DM Sans and DM Mono, paper #f4f0e8, black #0b0c0c and acid #d8ff38. The wordmark puts .dev in acid. Acid is a surface colour only, never a text colour on paper (too little contrast).
The counter from the productbuilder.dev hero is the family element: “1 builder”, “1 day”, “1 week”. prototypeinaday.dev uses acid as its dominant colour; mvpinaweek.dev is calmer and uses acid only for progress. The *dev sites do not use the Shit* plate system.
UTM parameters
Same rules as Graphic iDraw Rescue: only lowercase letters and hyphens, #anchor after the UTM tags. Links within one site get no tags.
| Parameter | Value |
|---|---|
utm_campaign |
star-dev (always) |
utm_source |
The site the link is on: productbuilder-website, prototypeinaday-website, mvpinaweek-website, tcf-website. Google Ads: google |
utm_medium |
website; Google Ads: cpc |
utm_content |
Place of the link: header, hero, cta, footer. Google Ads: the ad group, such as prototype-laten-maken or idee-testen |
productbuilder.dev links to conveniencefactory.com without UTM tags at the moment, and uses rel="noreferrer", so these visits cannot be traced yet.
Tracking: all three sites use @tcfbv/web-tracking (since 23 October 2026). The visible mail address is assembled in the browser; a visit with utm_source=google puts the channel code [g] in the subject of the mail, and each click sends one contact-mail event to Umami with place (the section id, such as hero) and source. Leads get the channel code in their notes in the TCF CRM; there is no separate channel field.
Timeline
- 24 September 2026: Maurice posted the first LinkedIn post (“Product Builder? Don’t you mean Product Owner?”), linking to productbuilder.dev. Kiliaan, CEO of Close, reposted it to their network.
- 2 October 2026: campaign renamed internally to *dev; offer sites moved to English
.devdomains;mvpinaweek.devandprototypeinaday.devregistered at Cloudflare.prototypeinaday.devlaunched on Cloudflare Pages. - 23 October 2026: web-tracking live on all three sites. New offer live: 8 hours for EUR 1,199 and 40 hours for EUR 5,999.
Market
- Close /
productbuilders.nl: Close (CEO Kiliaan, very experienced) uses the same angle onproductbuilders.nl. The site is live. Close offers senior engineers with 10+ years of experience, a fixed price per deliverable and a first working result within 6 weeks. Close targets organisations that would otherwise hire a large IT agency: corporates and mid-sized companies, not startups. We build the category together with Close and work with them informally, without formal agreements. Close serves corporates, we serve startups. There is no brand risk in using “Product Builder” in ads. See the meeting of 20 October 2026 for the possible joint company. - OneDayBuild /
onedaybuild.nl: a service of Appfront B.V. (Amsterdam). “Van idee naar app in één dag”, a team of designers and developers working one office day, EUR 1,150 excl. VAT, fully credited when a follow-up project starts within two months. Dutch only, three cases. Our difference: one senior builder, the repository, and a direct route to the MVP. We do not bid on their brand name.
Sales terms
- Contracts in English under Dutch law, signed digitally.
- EU customers with a valid VAT number: VAT reverse-charged; check the number in VIES at signing. To be confirmed with the tax adviser.
- An MVP requires a prototype first (internal rule, see Offer). No crediting of the prototype price.
Channels
Google Search ads (decided 9 and 23 October 2026):
- One campaign, about €10 per day (€300 per month), fixed for 8 weeks. Dutch keywords only, target area the Netherlands, landing site
prototypeinaday.dev. - Two ad groups: “Prototype laten maken” and “Idee testen”. Auto-tagging off; a Final URL suffix per ad group (see UTM parameters). Pin the description that says the site is in English to position 1. Do not bid on “one day build”.
- Qualified lead: an EU startup that mails with the three intake questions filled in, or calls, and then plans an intake. A click on the mail address does not count.
- Stop and scale: no qualified lead after €600: stop or rewrite the ads. Two or more qualified leads: scale to €400 per month. In week 4, check the cost per click and the bounce rate, because Dutch ads land on an English page.
- Do the first test click in Umami on production;
data-domainsblocks events on thedev.*previews. - Status 29 October 2026: the sites are in Google Search Console and Bing Webmaster Tools. Google Ads billing does not work yet; waiting for Google Support. Ads not live.
Organic:
- LinkedIn and Bluesky/X: build-in-public posts and short demo videos, such as a prototype day in three posts (hour 0, hour 5, the demo).
- Indie Hackers, r/SaaS, r/startups; dev.to for deeper articles.
- Product Hunt and Show HN once there is a working demo.
- Startup scene in the Netherlands and the EU: Techleap, Silicon Canals, accelerator Slack groups.
- Newsletters: TLDR AI, Ben’s Bites, Console.dev.
- Visibility in AI search engines (ChatGPT, Perplexity, Google AI Overviews): the sites already have
llms.txt, JSON-LD and question pages. Mentions on other sites matter most: dev.to, Silicon Canals, Techleap and accelerator guides. Once a month, ask Perplexity and ChatGPT the same question and note whether we are mentioned.
Measure per channel with its own UTM tag or short link, counted in Umami. No tracking pixels.