Founder & Ventures
GWK Ghostwriter
Situation
As Growing With Kid’s founder, I needed LinkedIn posts that sounded like me — grounded in source material I trusted — without rebuilding voice from a blank prompt every session. Generic AI tools forgot preferences, drifted tone, and treated research as disposable chat. The business need was a repeatable research-to-post workflow I would actually run.
Build story
At a glance
People affected
Primary user: myself as founder-operator publishing for Growing With Kid. Secondary: the same studio grammar intended to extend to Bolo Buddy and client tools without becoming a generic content mill.
The apparent problem
“I need better prompts” — as if quality lived in wording the model once correctly.
The problem underneath
Voice, beliefs, sources, and what worked last time were not system state. Without memory, scoring, and human approval boundaries, the tool optimised for fluent text that still failed the job: posts I could stand behind.
My mandate
Constraints
Critical decision
Situation
Build either a smarter prompt box or a system that remembers voice, sources, and feedback across sessions.
Options considered
Prompt-centric chat with saved snippets
Still treats every draft as a new conversation. Voice rules and sources stay outside the product’s memory.
Fully autonomous posting from calendar
Removes the human approval boundary. Brand and factual risk too high for a founder voice product.
Memory-backed studio with research → score → draft → preview → schedule
Observation
Running LinkedIn drafts in generic tools produced fluent posts that still drifted tone and ignored prior feedback. Source chats were hard to reuse. The job failed at continuity, not at sentence quality.
Insight
A full studio costs more surface area (dashboard, editor, knowledge, analytics) than a chat widget — but only a system with memory can stop voice drift.
Response
Ship a personal LinkedIn studio where preferences, style, feedback, and topics persist; ideas are scored from sources; drafts preview as LinkedIn; scheduling and analytics close the loop — always with human approval before publish.
Result
A workflow I can run: research to post with long-term memory and voice rules. Observed: live prototype and landing path; usage quality is directional while the product is still founder-operated.
How the system changed
Replaced the blank-prompt habit with a dashboard, post editor with live LinkedIn preview, ideas, calendar, knowledge base, memory, analytics, and voice profile.
Made memory core — preferences, style, feedback, and topics persist so the next draft already knows the rules.
Connected research to post: score ideas from source material, draft, preview, schedule, then read performance back into the studio.
Kept human approval as a hard boundary — the model never publishes alone.
Wrote the landing page as the product’s own conversion path, not a separate moodboard.
Validation and iteration
Without a durable voice profile, drafts sounded “AI-helpful.” Explicit beliefs and style rules in memory reduced drift more than longer prompts.
Knowledge-base material had to stay inspectable. Silent synthesis was rejected in favour of scored ideas tied to sources the founder can open.
Memory can overfit recent feedback. Forgetting and re-weighting what to remember remains an open product question.
Outcome
operational
Research-to-post loop with memory, voice rules, and source material a founder can operate end to end.
organisational
Writing rules and sources live in memory and knowledge — not in a one-off prompt.
business
Same studio grammar can serve Growing With Kid, Bolo Buddy, and client tools without becoming a generic mill — directional until those extensions ship.
Product
What I would change now
I would instrument before/after draft acceptance rates against a fixed voice rubric earlier, and define explicit forget rules so memory does not quietly become a junk drawer of every past preference.
Have a similar challenge?