One System for Content, Community, and Email That the Founder Runs Herself
A solo, non-technical leadership-development founder had deep IP but no system to run it, with content, members, and email split across three disconnected tools. I built one connected operation across Notion, Circle, and Kit, where she writes a piece once and it flows where it needs to go. Then I handed it over to an owner who understood none of the machinery on walkthrough day and was editing it herself two weeks later.
- Role
- Solo build. Architecture, multi-platform integration, and full handover.
- Tools
- Notion ,Zapier ,Circle ,Kit
What impressed me most was more than the quality of the build, it was the care he took to ensure I could confidently operate and evolve the system myself. Every detail, from the initial blueprint through to the handover kit, reference documentation, Loom videos, runbooks, and visual maps, was thoughtfully designed and documented.
Tamas has a rare ability to listen deeply, understand the intent behind the work, and translate ideas into elegant, practical solutions. He consistently found ways to simplify complexity while preserving the integrity of the vision.
If you're looking for someone who combines technical excellence with strategic thinking, clear communication, and genuine care for the outcome, I highly recommend Tamas.
Watch the walkthrough.
The problem
A platform designed everywhere, running nowhere
Deep IP, a tiered membership model, and a clear vision, but no system to operate it. Content lived in Notion, members in a community platform, email in a third tool. Every weekly publish meant copying content by hand into each one, in the right format, to the right audience. She knew exactly what she wanted and could not operate it.
The owner is the operator
This was never going to be handed to a technical team. A solo, non-technical founder would run it alone, day to day, after I left. The system could not just work. It had to be operable, editable, and ownable by someone who, in her own words, did not understand any of the machinery under it. A clever build she could not touch would have been a failure dressed as a delivery.
The feature she wanted most was the one her plan blocked
Auto-posting from Notion into her community was, to her, the heart of the whole thing. The community platform locks its API behind a Business plan costing roughly twice her entry-tier plan, and the popular integration tool wraps that same locked API. On paper, the feature she most wanted required an upgrade she did not want to pay for.
The solution.
Architecture diagram, click to zoom
One source of truth in Notion
I built four relational databases that hold the entire operation: a content engine for her weekly pieces, a library for her foundational IP, a member directory with her five membership tiers, and a distribution log that tracks where each piece has been published. They are wired together with relations, so a piece knows which IP it draws on and which channels it has gone out to. On top of them sit three dashboards and fourteen filtered views, so her daily screen shows what is in flight without her building a single query.
Publish once, flow everywhere
Four automations carry the work between tools. Mark a piece ready and it drafts an email broadcast for her to review and send. Mark it published and it posts to her community space automatically, with the formatting and visibility she chose. New email subscribers appear in her member directory, already sorted into the right tier. Unsubscribes move to an alumni status without her touching anything. She moves one field from ready to published and the system handles the rest, across three tools, in seconds.
The auto-post that ran on the cheap plan
I did not take the upgrade-or-skip framing at face value. First I verified the wall was real, testing the platform's tokens directly against its API to confirm the entry plan returned access-denied. It did. Then I found a route the gate did not cover. The platform exposes a second way in for its own automation connector, authenticating through a different permission scope that is open on the entry plan. So I built the auto-posting through it: a webhook fires from Notion the moment a piece is published, lands at the automation layer, and creates the post in her community through the connector route. End to end, live, on the plan she was already paying for. She never upgraded.
The handover that stuck
The engagement was built around her independence, not mine. After delivery, a deliberate owner-success phase ran on release criteria defined entirely by her: could she publish a new piece end to end on her own, add a member and see them land in the right tier, change the structure herself. I guaranteed the risky part in plain terms, the automations would be live and working by handover or I would keep working at no extra cost until they were. The handover kit was nine documents and three short walkthrough videos: a weekly operating procedure, a reference doc, a runbook of what tends to break first and how to fix it, and a prompt pack for drafting content, written so she could hand the whole system to a future assistant without ever reopening the architecture.
The impact
Delivered
- One connected system across Notion, Circle, and Kit, write a piece once and it flows to email, to her community, and into her records
- Four relational databases, three dashboards, and fourteen filtered views as the source of truth
- Four live automations carrying the work between tools, plus smaller in-Notion automations keeping the distribution log in sync
- A nine-document handover kit plus three walkthrough videos, built so the system can pass to a future assistant
The handover that stuck
- A post-delivery owner-success phase measured only by what the founder could do unaided
- The auto-post she cared about most shipped on her entry plan, with no upgrade and no doubled monthly bill
- Within two weeks she rerouted one of the automations to a different destination in her community and renamed one of her membership tiers, both by herself, both without asking first
- "What you've done is amazing. I don't understand any of it, except it's brilliant."
Have a similar problem?
Tell me what is going on and I will tell you what I would do about it. No obligation.