Most teams don't have an AI problem — they have a few people using AI and no shared system underneath it. I build the knowledge layer that makes AI something your whole team can actually use.
Explore a service, then tell me what you need.
Every engagement starts with an audit of how your work actually happens.
I design or rebuild your workspace around your workflows, so the business can run beyond what's in your head.
Connected databases, dashboards, and practical documentation, with training so your team can run the system confidently.
I map where information lives, how it connects, and who keeps it current across your tools.
A knowledge architecture with clear ownership, documentation standards, and a practical plan to put it in place.
I identify where AI can help, then build the shared context and workflows it needs to work reliably.
AI assistants, automations, or shared prompt systems matched to your needs, plus training to help your team use them.
I stay involved as your team grows, taking care of the upkeep and improvements that otherwise get pushed aside.
Hands-on execution, system maintenance, workflow improvements, and ongoing support focused on your team's priorities.
Async-friendly · Clear scope · Custom proposals
Not sure where to start? Let's figure it out together.
Tell me what's going on →I never prescribe before understanding. Every engagement runs the same sequence — because the order is the method.
I learn how work actually happens — not how it's supposed to. Tools, workflows, documentation, and the things quietly living in people's heads.
A structure mapped around your team's real behaviour. You review and refine the design before a single thing gets built.
Workspaces, documentation, integrations, AI workflows — built carefully, scoped clearly, delivered on a flat fee with no surprise invoices.
Walkthrough, training, and transition notes. Your team can run it without me — though a lot of them choose to keep me around.
A few things I've untangled.
Open a folder to look inside.
One connected Notion system for inquiries, bookings, and event details.
Open case study 02 / Creative agencyClear roles for Notion, Asana, and Slack, connected into one workflow.
Open case study 03 / SaaS · 100+ peopleA knowledge architecture that makes it clear which documentation is current.
Open case studyI'm Jelly. Before consulting, I spent over a decade as an operations and executive assistant — usually the person quietly holding the process together while it lived in someone's head.
That's why I audit before I recommend anything. I've seen what happens when systems are designed without watching the work. Now I work directly with founders and growing teams, from the first audit to the final build. No account managers, no handoffs — just me.
Give every tool a clear job.
Give the whole team shared context.
Built from real client engagements — not brainstormed templates. If you're not ready for a full project, start here.
A 53-page guide to building Notion workspaces teams actually maintain — structure, documentation, and the decisions behind them.
Paid guideGumroad →An AI-ready knowledge management starter kit — structure your business context so AI tools can finally deliver something useful.
Coming soonGet notified →Six free templates from the Notion marketplace — starting points pulled straight from systems I've built for real teams.
FreeBrowse →Tell me what feels messy. I read every inquiry myself, and if I'm not the right fit I'll say so.
Tell me about your project →Thoughtful systems, built to evolve.