Add commentEdit

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

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

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

What to agree with the client before starting

During the work

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:

  1. The term. People do not know “Product Builder” yet, and often assume it means Product Owner.
  2. 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

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

Market

Sales terms

Channels

Google Search ads (decided 9 and 23 October 2026):

Organic:

Measure per channel with its own UTM tag or short link, counted in Umami. No tracking pixels.