01
Source hierarchy
Every conclusion points to the governing source. Conflicts and missing context are surfaced, not invented.
For businesses that run on leads
Your leads come in through ads, forms and partners, and disappear into separate tools. We bring them together in one overview and route them automatically to the right follow-up. No lead falls through the cracks anymore.
I want to use this for
After 30 minutes you have one workflow, its largest quality risks and a concrete pilot scope.
Quality gate passed
CRITICAL0
Output quality
measured
measured
Scroll
How it works
From fragmented leads to one routed flow.
2-3weeks to first evidence
First we define what good looks like. Then we build and test in shadow mode, without irreversible actions.
WHY OUTPUT QUALITY MATTERS
He found out after five months that he was not properly insured. Cost: $30,000.
The problem was not a lack of software. The governing rule, owner and escalation path did not exist as one executable standard. An agent without that structure could work faster and still make the same mistake. That is why Studio Zakai starts with the definition of correct, not with the tool.
$30,000One missed deadline, one time
WHAT WE DELIVER
Six fixed quality controls, independent of the runtime.
Your operating standard remains portable when the runtime, model or vendor changes.
The Workflow Blueprint and Knowledge Pack capture the operating method. The Quality Contract defines which output is good enough and when a change may reach production.
02
Decision rules
Categories, thresholds and failure conditions are made explicit before an agent executes the process.
03
Exceptions and approvals
We define when the workflow stops, who decides and which permissions are deliberately withheld.
04
Fixed evaluation set
Real, approved examples test classification, content, style and critical failure checks.
05
Release gate and rollback
A new prompt, rule or model version only goes live after a passed test and explicit approval.
06
Monitoring and feedback
Corrections, incidents and reviewer edits are stored append-only and inform the next candidate version.
The quality cycle
Before buildSources, rules, exceptions and owners are approved.
Before releaseThe candidate version runs against the same fixed evaluation set.
In productionCritical failures, overrides and exceptions remain visible.
During improvementA reviewer approves both the change and the evidence behind it.
Feedback therefore never pushes a prompt live automatically. The system proposes a candidate improvement, tests it and waits for approval.
In practice
Built around real work.
Studio Zakai works on marketing operations at scale, international obligations and a safari back office. The implementation changes, the quality layer stays consistent.
De ZaakIn production
Marketing operations on a platform serving 144,000 entrepreneurs
Lead routing, campaign workflows and reporting run on one operational layer with more than six live integrations.
Next.js · Supabase · LeadByte · Copernica · Moneybird · Meta
International operationsIn use
Obligations monitored across five countries
Two CEO environments bring sources, owners, deadlines and escalations together without giving away decision authority.
Source hierarchy · Deadline monitoring · Human approvals
Safari back officeIn development
Rate data out of scattered price lists
The first tariff database turns lodge price lists into source-backed rate rules. Booking steps, payment moments and documents follow in the same back office.
Tariff database live · Booking flow in development
Justus Fokker
Studio Zakai · Amsterdam & Nairobi
Studio Zakai · Amsterdam & Nairobi
WHO BUILDS IT
A former lawyer who treats critical workflows like case files.
I am Justus, founder of Studio Zakai. My legal background taught me to capture sources, exceptions and accountability precisely. As a systems builder I make that logic executable and testable.
I do not sell a model or server as the solution. First we define correct output. Then we build and test the workflow in the environment that fits best.
You work directly with me. Your company keeps the data, accounts, decisions and portable documentation.
Legal precisionSources, rules and exceptions remain traceable.
Runtime neutraln8n, Cowork, Copilot or custom code are execution choices.
Client ownershipData, credentials and decision rights remain yours.
Next step
Map one critical workflow clearly.
We take your lead flow and sources as an example and show what your overview will look like. Concrete, tailored, in 30 minutes.
Book your workflow scan
After 30 minutes you have the sources, quality risks and a bounded pilot scope in view.
Studio Zakai© 2026 Studio Zakai