Implementation story · June 2026
Janet: an assistant for a senior marketing role.
I built Janet as a dedicated assistant workspace for a VP of Marketing at Sifted. The aim was to give the assistant the context of the role, reusable ways to work and clear boundaries around actions that need approval.
The starting point
Give the assistant a place to understand the job.
A senior marketing role carries context across briefs, decisions and recurring work. The setup needed a dedicated place for that context, with reusable instructions for the assistant and a clear place for its owner to review the work.
I built Janet using OpenClaw, with role context, reusable tasks and a dashboard. Its owner could review the work before anything was sent or changed.
How the setup fits together
Context, reusable work and a human decision.
The assistant prepares the work and brings it back to its owner for review.
01 · Approved role context
The job, working knowledge and instructions the assistant needs.
02 · Reusable skills
Repeatable ways to prepare work using that context.
03 · Dashboard
A command centre for organising work and bringing it back for review.
04 · Owner review
Drafts and proposed actions reach the owner. External actions require approval.
What was checked
The setup and its approval boundaries.
I checked the workspace setup, ran diagnostics and rehearsed the support process. I also tested that changes to HubSpot were blocked without approval.
A distinct workspace
Janet had its own role context, dashboard and reusable tasks.
Visible boundaries
The owner reviewed external actions first. I tested approval checks for HubSpot changes; a full CRM or calendar integration was not part of this build.
Setup and support checks
I ran diagnostics and rehearsed support, then removed the temporary support access.
What this example shows
An implemented assistant setup.
This describes the setup I built in June 2026, rather than a company-wide rollout or endorsement. I haven’t measured its effect on time, productivity or revenue.
It is a snapshot of that build, not a statement about how the assistant is being used today.
Your recurring work
Tell me about one task you would like to improve.
A weekly brief, a campaign handover or an assistant that keeps missing the context is enough to start a conversation. We can decide what a useful first version would look like.