Builder workspace
This is where the template route becomes a real workspace. First you choose the right foundation, then shape atmosphere and content, and only after that move domain and launch steps forward when the package and operator layer allow it.
01
Each builder entry point should already fit its context. You are not choosing a loose skin, but a route with the right atmosphere, sections and conversion logic.
Template family
For artists, labels and makers who need a distinct world fast.
The base stays narrative and visual. Inquiry handles briefing or booking, while gallery and agenda expand proof and context.
Active workspaceTemplate family
For camping, stay and hospitality routes where calm and trust matter most.
The base carries the atmosphere, but booking carries the main action. Inquiry still works for custom stays or group requests.
Open this routeTemplate family
For coffee bars, food spots or small service businesses that need a strong fast start.
Offer and presentation need to feel right immediately. After that, the business decides whether the main action is inquiry, booking or ordering.
Open this route02
Route config, modules, package choice, domain intake and registrar preparation come together here inside one saved project state.
Builder MVP + phase 2
Not just route config and renderer, but package selection, domain intake and a gated project flow that shows how this route can actually move toward launch.
Route family
Choose the foundation that already fits the client or business type.
Best for
For artists, labels and makers who need a distinct world fast.
Primary moment
The first conversion here is often recognition. The route needs to land atmosphere, work and credibility before anything else.
Inputs
Theme
Atmosphere shifts, but the quality bar stays fixed.
Preview size
Phone keeps a tight frame. Laptop and wide show the route on a fixed canvas width without distortion.
Route logic
Each route family carries a different primary action and different useful add-ons.
The base stays narrative and visual. Inquiry handles briefing or booking, while gallery and agenda expand proof and context.
Active flow
The inquiry layer moves visitors from atmosphere into action without turning the route dry or corporate.
Recommended starter set
Package and access
The route does not stay fully open to the public. Package selection decides how far it may actually move forward.
Domain intake
This is intentionally not a live registrar check yet. First we screen format and extension server-side, only then may a real backend lookup follow.
Domain state
No domain screened yet.
Next registrar step
After screening, package and operator layer decide whether registrar lookup may begin.
Project flow
This shows how a route moves from editor into gated launch without opening a cost leak.
Shape route
Foundation, atmosphere, modules and editor output.
Screen domain
Format and intake screening only, not live registration yet.
Unlock access
Only after package selection can the workspace actually continue.
Launch queue
Registrar, DNS and operator launch stay server-side.
Launch profile
This is the final layer before the real registrar. We collect the operator and registrant information for the handoff here. KvK is not treated as a hard blocker in this flow.
Provider route
Registrant type
Launch gate
Registrar handoff stays closed until this route sits in Managed Launch.
Modules
Add-on layers on top of the base route, not hidden inside it.
Live preview
Artist / maker
A route for makers who do not want to look generic online.
Route for
For artists, labels and makers who need a distinct world fast.
Base sections
Package layer
Kickstart
Domain intake
Not screened yet
Conversion layer
The inquiry layer moves visitors from atmosphere into action without turning the route dry or corporate.
Flow steps
Field base
Project flow
Shape route
Foundation, atmosphere, modules and editor output.
Screen domain
Format and intake screening only, not live registration yet.
Unlock access
Only after package selection can the workspace actually continue.
Launch queue
Registrar, DNS and operator launch stay server-side.
Operator note
This mode keeps the route in intake and discovery until the right package is chosen.
03
The builder intentionally stays behind guardrails. Clients can move forward without paying for everything at once, and without instantly unlocking publishing, registrar actions or provisioning in public.
Access
Included in intake
For first route selection, domain screening and a guided intake without open builder access.
Strong when the client needs direction fast but should not yet unlock publishing or provisioning.
Access
+ €15 / month
For clients who want to save, continue and shape the route further within guardrails.
Fits the fast template client who wants more autonomy without directly triggering live registrations or provisioning.
Access
+ €35 / month
For routes that may move from intake into real domain registration, DNS and launch preparation.
The best bridge between template speed and serious go-live without letting the client touch infrastructure directly.
04
Not everyone needs everything open on day one. This sequence keeps the route sellable, manageable and credible, while the entry point stays compact and heavier costs only start later.
Kickstart
Strong when someone is still finding the right route, atmosphere and domain direction, but does not yet need independent builder access.
Route Plus
For clients who want to continue seriously with their route and shape it inside guardrails, without touching live infrastructure yet.
Managed Launch
This is where the route moves into real domain registration, DNS and launch preparation, while still staying under operator control.
Next move
From here we can keep building toward publishing logic, intake follow-up and deeper modules without reinventing the route every time.