Eighteen specialists. One shift.

a team, not a tool

Is this a tool or a team?

A tool waits until you open it. This team does not. The shift starts at 22:30 whether I am there or not, and by 07:00 there is a briefing on one page.

That is the whole difference. I do not sit in a dashboard assembling prompts. I read what came out and I say yes or no. Strategy, SEO, content, design, outreach, advertising, data, branding and publishing each have an owner, and each owner reads what the previous one produced.

the crew

Who are the eighteen specialists?

The same eighteen every night, in the same order. The codes match the timeline on the homepage; the times are when each specialist starts.

Role	What they do	Starts
CSChief of Staff	Opens the shift: reads yesterday’s outcomes, sets tonight’s focus, guards the escalation cap.	22:30
CRCRM	Data hygiene before anyone touches a lead: validates, normalises, flags what needs enrichment.	22:45
OUOutreach	Researches leads, enriches them via LinkedIn, prepares personalised outreach as drafts.	23:00
SESEO	Tracks our own rankings and technical health, flags first-mover keyword opportunities.	00:00
MIMarket Intelligence	Watches competitors and buying signals, hands hot signals to outreach.	00:30
COContent	Writes blogs and page copy in the target language, then runs the humanity and brand checks.	01:00
GVDesign	Checks the live site page by page, produces visual fixes and assets.	02:00
PUPublishing	The only one allowed to publish. Works the publication queue at approved times.	02:30
BDBusiness Development	Researches one revenue theme per night, builds toward a weekly executive report.	03:00
GRGrowth	Measures the whole funnel and writes the dashboard the rest of the team reads.	03:00
EMEmail Nurture	Maintains the email sequences and the monthly newsletter.	03:30
CDCreative Director	The visual gate: approves every visual or sends it back before it can ship.	03:45
BRBranding	The text gate: reviews all outward-facing copy for the right title, numbers and tone.	04:00
SMSocial Media	Plans LinkedIn content and scouts speaking opportunities.	04:30
MSMarketing Strategy	Reads everything the night produced and writes tomorrow’s assignments.	05:00
ADAdvertising	Pulls the paid channels daily and advises. Never changes a campaign without a human go.	06:15
AIAI Research	Tracks the AI landscape and installs new capabilities for the team.	06:30
SKSkill Scout	Scans for new skills and tools per specialist, every week.	07:00

one night

What happens between 22:30 and 07:00?

A fixed route, Amsterdam time. Research first, production in the small hours, the two gates after that, and numbers before the day starts. Station by station, and if you are reading this at night, the line below shows where the shift is right now:

22:30 to 07:00, Amsterdam time

handoffs

How do eighteen specialists work together without meetings?

Handoffs are files, not chat. Each specialist ends the run by writing what the next one needs, and each run starts by reading what is there. Nothing depends on someone remembering something.

Every handoff is typed: a task, an insight, data, a review request or a blockade. Each carries a priority, P0 to P2, and P0 goes first. A missing tool or missing access becomes a blockade handoff with a proposed fix, never silence.

Requests across teams need a cited goal. A specialist who wants something from another team has to point at the objective it serves; a request without one gets parked for the team leads instead of eating the night. Managers sync at fixed points, not ad hoc.

the gates

Who can stop what?

Everything that goes outside is closed by default, and there are four brakes before the door.

Text passes the brand gate, which checks the job title, the numbers and the tone against one source of truth. Visuals pass the creative gate, which approves or sends back, nothing in between. Code passes security and quality reviews. And publishing is a monopoly: exactly one specialist is allowed to press publish, so an approval elsewhere never accidentally becomes a publication.

Two more brakes are about me. The team may escalate to me at most three times a day; a fourth question waits for tomorrow unless the website itself is broken. And content written at night publishes at human times, on a Tuesday or Thursday morning, not at 03:00.

That this is real is easiest to see when it bites. Two security reviewers gave my first product release a hard fail: XSS through innerHTML, unvalidated input, prototype pollution. They were right, and it only shipped after the fixes.

Run your own copy past the brand gate →

proof

What has it actually shipped?

This team took PlainConsent from the first line of code to a live site with paid tiers. It builds and markets Sterka, which is in production with real users. And it runs my own marketing while doing it, including the site you are reading.

It also gets things wrong, and I publish those too. One specialist used the wrong job title in external copy for months before I built a separate gate for it. My two websites carried the same number with a factor 66 difference, and nobody flagged it but me.

What broke, concretely?

Build in public only works if the failures have dates on them. The three most recent, measured, not remembered:

the product version

What is Ensemblo, and how does it relate to this team?

Ensemblo is this team, productised for Dutch companies that do not have one. Eight specialists instead of eighteen, because a company that is starting out does not need a night shift of eighteen. You send a message, your team does the work, you approve with one click.

I only started selling it after it had run in my own business for a year. That order matters: first it had to work here, then it could be sold.

ensemblo.nl →