About
Built so AI writes for your brand,
not over it.
Anyone can generate content now, which is exactly the problem. The web is filling up with copy that sounds like everyone and belongs to no one. cpywrk exists to fix that: it runs the research, drafting, and quality checks end to end, while the people who actually know the business keep control of the voice. Fast where speed helps, human where judgment matters.
Team
The key players behind cpywrk
One founder owns the direction. A team of AI agents each own a single craft, from research and design to engineering, SEO, and the brand's voice. Here is who does what.
Founder
Klaas Hermans
Founder, cpywrk
I wanted to create a content platform that lets companies use AI without letting it run off with the brand voice. cpywrk does the research, drafting, and checks; the people who actually know the business keep the keys.
Connect on LinkedInThe agents
One craft each.
Every one is an AI agent with a single job and a clear lane. A tech lead routes the work, specialists execute, and nothing ships without review. The same shape as the pipeline that writes your content.
-
Marcus
Tech lead
Reads the state of the build, decides what happens next, and routes each task to the right specialist. Keeps the project moving and the quality bar high.
-
Ava
Researcher
Digs up market context, competitive angles, and the evidence a decision needs, then returns it with explicit confidence levels, not hunches.
-
Leo
Product marketer
Owns positioning and messaging: who cpywrk is for, what to say, and how each feature is framed for the people who will actually use it.
-
Iris
Brand voice
Guards how cpywrk sounds. Turns approved messaging into copy that reads like the brand: specific, plain, and never generic SaaS filler.
-
Noor
SEO, GEO & AI search
Owns technical and on-page SEO and structured data. Tunes every page to surface in AI answer engines, not just classic search results.
-
Priya
UI/UX designer
Designs the flows, layouts, and component specs before a line is built: implementation-ready, always in the shared design system.
-
James
Frontend developer
Builds the interface from Priya’s specs: accessible, fast, and faithful to the design, wired to Sofia’s APIs.
-
Sofia
Backend developer
Owns the data model, API routes, and the async jobs that run the pipeline, the machinery customers never see but always feel.
-
Dan
DevOps
Wires the services together and ships them: hosting, environments, and the deployment plumbing that keeps everything online.
Agentic, but not unattended. A human owns the direction and signs off on what ships. The same principle the product is built on: speed from the agents, control kept by people.
Want a team like this writing your content?
One article free. No card required.