Systems and processes I've built to keep businesses running smoothly.
Each client has a separate published dashboard, so no client sees another's data.
One portal tracks a sprint-based client, the other a retainer-based client with hours used and renewal date.
An internal view of every client and project gives the agency one place to see everything.
A Notion client portal built for a fictional creative marketing agency. Each client gets a separate workspace, so no client can see another's data: one sprint-based client (Verdant Skincare) and one retainer-based client (Northbridge Software). Every portal has a Projects database, Deliverables/Assets and Feedback/Approvals databases linked two-way to Projects, and a dashboard showing active work, items awaiting review and anything needing attention.
Built as a self-initiated project for a fictional agency, using the requirements of a real job post as the brief. Not paid client work. Client separation is simulated with individually published pages rather than separate Notion workspaces, and the internal agency summary is populated manually.
A combined personal and business Notion workspace for a fictional solo marketing and brand consultant, so her client work and personal life live in one system without duplicate data. Linked Clients, Projects, Tasks, Invoices and Quick Capture databases feed an At a Glance dashboard showing what is due this week, active projects and invoices needing attention. A Days Overdue formula flags late invoices instead of relying on a manual status. Personal and Business sit on separate sub-pages so the business side can be shared with an assistant on its own.
This project is presented as a walkthrough video. Built as a self-initiated project for a fictional client, using the requirements of a real job post as the brief. Not paid client work. Page-level sharing permissions are documented in the design but not configured on a live account.
Personal and business tasks sit in one Tasks database, separated by a Life Area field and views, so nothing is entered twice.
A Days Overdue formula flags late invoices, so there is no manual status to keep updated.
Personal and Business sit on separate sub-pages, so the business side can be shared with an assistant on its own.
Relational databases linking clients to their sessions, packages, and remaining balance.
Session counts and overdue payments track themselves, with no manual updates.
One homepage view surfacing active clients, upcoming sessions, and overdue invoices.
A complete Notion workspace built for a health coaching business: four connected databases (Clients, Sessions, Contents, and Invoices) linked by relations, with formulas tracking session counts and overdue payments automatically, and filtered views surfacing what matters each week at a glance.
This project is presented as a walkthrough video. Built as a self-initiated project for a fictional client, designed to demonstrate a niche-specific Notion system for coaches and consultants.
End-to-end operational system for a self-run small business — customer communication, order handling, and invoicing tracked across multiple systems to avoid single points of failure. Built and maintained a customer base of 12 clients, including repeat buyers, without a physical shopfront.
This project is presented as a walkthrough video with sensitive information blurred. Click below to view the full system in action.
Structured messaging workflows across channels
End-to-end tracking from inquiry to fulfilment
Consistent records across multiple systems
The day-to-day admin behind the systems.
Numbered folder structure and file naming for a fictional architecture project.
A Notion system for planning and tracking a long-running personal project: an 8-phase breakdown with task-level checklists, a build-tracking database and a categorised reference-image library.
I approach every project the same way: break it into clear phases, track status honestly instead of guessing, and keep the structure visible — even on long projects with no one checking in but me. Systems don't have to be complicated to work. They just have to hold up when things get busy.

Every project starts with a clear structure. No ambiguity about what comes first, what comes next, or what done looks like.
Progress is visible and accurate — not optimistic. If something is blocked, the system shows it before it becomes a problem.
Good systems are readable at a glance. Anyone stepping in — including future me — should be able to orient immediately.
The real test of a system is when things get busy. These are built to stay functional when there's no time to think about the system itself.
These projects represent real systems I've built — running my own business, and through self-directed training designed to mirror real client work — all with the same standard of care. Each one was designed to be handed off, scaled, or picked back up after time away without losing context. I work best in the background: setting up the infrastructure that lets other people focus on what they do best. If your business needs cleaner systems, better organization, or someone to own the operational details — that's where I come in.
Each project shown with screenshots or a walkthrough
Systems, scheduling, files, and communication
Built to hold up when things get busy
I'm available to build Notion systems for coaches, consultants, and small teams, plus operations and admin support. If you're looking for someone to design the systems that keep your business running, let's talk.
Projects