Sales-call prep
Before: About a day. In practice, skipped.
1 hour
Walked into the call prepared.
Two call transcripts in. Key quotes and what to watch for out, on one page.
Second brain
Stop starting from zero.
Your knowledge, voice and clients in one place your AI reads first. Your work starts as a draft, not a blank page.
Built in Claude Code · Your files, your accounts · Polish or English
A recent build · first two weeks
What took a day, or never got done, now takes an hour.
Client worksheets
Before: 4 hours, for a plainer version.
1 hour
Branded and consistent. The client noticed.
Built from the method, brand and notes already in the system.
Miro workshop board
Before: Tried once. It failed. Gave up.
1 hour
Built straight in Miro. The client loved it.
Course lessons in. A full board of frames out, after 3 rounds of edits.
Reported by the client, a solo consultant. No custom agents yet: the foundation alone.
What changes
Less writing. More finished work.
No blank page
Your work starts as a draft.
Instead of an empty page and two hours
Sounds like you
Your phrases. Your tone.
Instead of rewriting chatbot text
Hours back
Repeat work in about an hour.
Instead of an afternoon per task
One place
Notes, transcripts, files - connected.
Instead of nine tools that don't talk
Ideas kept
Voice notes turn into work.
Instead of ideas lost in old chats
Yours
Plain files you own.
Instead of rented agents that can vanish
How it works
Your knowledge in. Finished work out.
You bring
- Notes and old decks
- Call transcripts
- Voice notes
- Your methods and cases
- Texts you wrote
Your second brain
One structure your AI reads before every task.
You get
- Call prep
- Proposals
- Client materials
- Workshop boards
- Posts in your voice
- Tasks from voice notes
- Weekly reviews
- Work from your phone
How I build it
Context first. Prompts second.
Weak AI output is rarely a prompt problem. The tool knows nothing about you. So I start with your context.
Start from what you have
Nothing deleted. Every change backed up first.
One clean structure
Eight folders. Locked top level. Rules in two files.
Every output is a file
Fix a sentence in 30 seconds, not 15 prompts.
Agents built from results
Matched to outputs you already like. You judge results, not prompts.
Simple first
One tool at a time. No servers until you need them.
You own it
Your files, your accounts. Keep it all if we stop.
How it runs
Six steps. Each one ends with something you keep.
- 1 90 min
Discovery call
You get
Where your time goes, and what to build first.
How
Your goals, your repeat work, every tool you use.
- 2 a few days
Plan
You get
A written plan with a fixed scope.
How
In your words: what we cut, what we build, in what order.
- 3 90 min
Interview
You get
A working second brain.
How
Claude interviews you in your own setup. It reads what you have and shows every file before saving.
- 4 1 h each
Working sessions
You get
Something new working, every time.
How
Tools connected one by one. Every session gets its own page.
- 5 in the sessions
Your agents
You get
Agents that sound like you.
How
Built against outputs you already like.
- 6 with support
Handover
You get
A system you run and grow yourself.
How
Support continues after the build.
What you end up with
A system you can open, read and change.
- 8-folder structure
- Rules in 2 files
- Your profile
- Your voice
- Knowledge base
- Process playbooks
- Connected tools
- Voice-note route
- Your agents
- A page per session
CLAUDE.md hard rules, read first
1-Daily/ voice notes, journal
2-Inbox/ materials to process
3-Clients/ one folder per client
4-Projects/ sales, content, goals
5-Knowledge/ your methods, cases, brand
6-Raw/ originals and backups
7-System/ rules, voice, agents
8-Outputs/ drafts, reports, decksIs it for you
Is it for you
Good fit
- You sell your expertise: consulting, coaching, a small agency.
- You use AI weekly and keep re-explaining yourself.
- Your know-how lives in notes, transcripts and old decks.
- You'd rather edit a draft than write from scratch.
Not a fit
- You want content on autopilot.
- You want it all inside a phone chatbot.
- You can't spare 90 minutes to teach it who you are.
- You want a black box you never open.
Questions
Questions
Do I need to be technical?
No. I do the engineering. You'll know what every file is for.
What do I need?
A Mac or Windows computer, a paid Claude plan and 90 minutes for the interview.
I already have notes and a setup.
Good. We build on them. Nothing gets deleted.
Where does my data live?
In your own files. Client material in your Google Drive. Model training on your chats switched off.
How long does it take?
About a month of sessions, at your pace.
What does it cost?
A fixed price, set after the discovery call. Not hourly.
Polish or English?
Both. Your materials can be in either.
Start with one call.
Tell me how you work. I'll tell you what I'd build first, or that I can't help.