Proposal OFF-2026-0008 · 31 August 2026
A six week 1:1 AI coaching programme for Andy Young, Interim Director of Design at PandaDoc. Built around the bridge you described, and run entirely in a sandbox of our own so nothing touches your employer.
01 · The brief, in your words
This programme is built on these four sentences.
"It feels like the whole organization is speaking English and I don't have the words."
On being a service designer in an org where 60% of R&D is engineering
"There's something about that bridge that feels too far to leap into. GitHub feels like reading Latin."
On the gap between Claude, where you are comfortable, and terminal, Cursor and code, where you are not
"I want to know enough to understand what's going on. Not at their level, but enough to feel like I know what sleight of hand looks like."
On what fluent actually means for you. This is the brief.
"My idea of play does not look like building stuff in the evening. I'd much rather get lost in fiction."
On the honest constraint most coaching ignores
One more thing you said, which changes the design of this programme
You are paying for this yourself, deliberately, because you wanted an outside perspective. That means we should not be working in PandaDoc's repositories or on PandaDoc's documents. So we will not. We build our own.
02 · Where we work
In session one we stand up a fictional agreement-automation product. Same shape as the thing you work on every day: documents, templates, signing flows, a design system, a backlog of real looking bugs. None of it belongs to anyone.
Nothing here is production, nothing is under NDA, and no colleague is watching. You can ask a stupid question, get it wrong, and go round again. That freedom is the whole point, and you do not get it inside PandaDoc.
Inkline is deliberately shaped like PandaDoc: a document editor, a template library, a signing flow, an audit trail. So every pattern you learn on Inkline transfers straight to a conversation with your own engineers on Monday.
The setup stays on your machine. It is where you try things for the rest of your career without asking permission or exposing yourself, which you cannot do at work.
01
You talk
Hold a key and say what you want, in your own words, at the speed you think. Wispr Flow types it wherever your cursor is.
02
The agent works
MCP connections let it reach the tools directly. It reads, builds, revises. Overnight if you want, so a question on Monday is an answer on Tuesday.
03
You judge
The work comes back as something you can look at. You click an element, say what is wrong, send it back. The loop you already run with your designers.
Notice what is missing. You never open a terminal and you never open GitHub. You already closed a ticket at work with the fix agent and called it the most significant thing you had done in six months. That was this loop. We make it something you can run on a Tuesday.
03 · The programme
Every session runs a craft lane and a leadership lane. The craft lane is what you can do. The leadership lane is what it means for how you run a design org of 36 people. They compound together from session one.
Wispr Flow
Hold a hotkey, talk, and it types wherever your cursor is. Your way into every other tool.
VS Code
The window everything lives in. A home base, and never a place you write code.
MCP connections
The wiring that lets an agent reach your tools directly and act for you.
Lavish Editor
Agent work comes back as a page. You click an element and say what is wrong.
Pen.dev
An infinite design canvas an agent can build in, so a prototype exists to react to.
Week of 8 September
We set up your voice, your window and your first MCP connections. Then you use them on a real design question: you talk, the agent goes away and works, and it comes back with a point of view you did not have to read for four hours to get.
Everything is wired before you arrive. You speak, you read, you decide. That is the whole session.
Craft lane
Wispr Flow, VS Code and your first MCP connections, running. The skill underneath is asking a sharp question. "Where would you cut scope here, given we cannot slow engineering down" beats "analyse this", and you will feel the difference in what comes back.
Leadership lane
Ask your senior designer the same question you asked the agent, and compare the two answers. The gap between them is your judgement. That is the part your team pays you for.
Week of 22 September
A prototype is waiting for you on a canvas, built by an agent from a brief. You open it in Lavish, click the thing that bothers you, say why out loud, and send it back. It returns changed. You go round again.
This is the loop you already run with your designers every week. Same judgement, different collaborator, and a much shorter wait.
Craft lane
Lavish and Pen.dev over MCP. The skill is feedback specific enough to act on. "Users get stuck here because nothing tells them it is editable" gets you a revision. "Make it better" gets you noise.
Leadership lane
You directed that prototype without building it. We name what that is, because it is the move your designers make in Figma every day, and it is the answer to the senior product director who out-builds your team.
Week of 6 October
No new tools. We take the work from the first five weeks and turn it into something you can say in a room. Then I play the sceptic, the engineer or the designer who thinks this is hype, and you answer.
You came in saying the organisation speaks a language you do not have. This session is where you find out how many words you picked up.
Craft lane
Nothing new to learn. We tune the practice: which questions are worth an overnight run, where the loop earns its keep in your week, and where it does not.
Leadership lane
Your position, rehearsed against pushback. Specific enough to survive contact: a tool, an artefact, one concrete change to how you run design critique.
04 · The thread
You asked what a successful executive design leader who genuinely uses this technology looks like. Nobody can hand you that answer in a final session. You build it in pieces, and each piece comes from something you actually did.
After session 1
You can ask
A question sharp enough that what comes back surprises you.
After session 2
You can direct
Feedback specific enough to move a design, and you can predict what it will move.
After session 3
You can hold the room
A position you have defended out loud, earned from work you actually did.
05 · How this respects your life
You told me straight that building things in the evening drains you and that Netflix wins. So the work sits inside your working week, on outputs your job already demands. If it does not save you time on a Tuesday, it does not go in.
You will not open GitHub and you will not type a command. The agent does that through MCP while you direct it. Your job is the question and the judgement, which is the job you already have.
You said you do not feel safe having this conversation at PandaDoc. These sessions are that room, and the sandbox is why it stays true: no company code, no company documents, no exposure.
Pre session intake. I review your tools and recent AI attempts before session one, and prepare your environment.
Async follow up between sessions. Message me when something breaks. This is where most of the value lands.
Recordings and transcripts of every session, sent to you.
Your whole setup, configured and yours to keep: voice, window, MCP connections, canvas.
Everything we build stacks into one place that is yours: the transcripts, the prompts, the agents, the decisions. By session three it is a small system of its own, and it keeps working after the programme ends.
This is the part that compounds. A two day course cannot.
06 · Investment
These are my published 1:1 rates. Sharpen is the one I recommend, and the one this proposal sets out.
| Option | Shape | Investment |
|---|---|---|
| Spark | One session of 60 minutes. Credit applies if you upgrade later. | EUR 450 |
| SharpenThis proposal | Three sessions of 60 minutes over six weeks, plus intake, sandbox and async follow up. | EUR 1.200 |
| Embed | Six sessions of 60 minutes over three months, woven into multiple parts of the job. | EUR 2.200 |
On VAT. Prices exclude VAT. VAT is worked out at checkout once you enter your billing address, shown as its own line, and it follows the rules for where you are. You get a proper invoice either way.
On upgrading. If session two makes it obvious you want the longer run, the difference to Embed is EUR 1.000 and we keep going. No new proposal, no restart.
On timing. The dates above are proposals. You mentioned a shorter run would suit you, so compressing this into four weeks is fine by me. Say the word and I move them.
07 · Approve
EUR 1.200Sharpen · 3 sessions over 6 weeks
Excluding VAT, added at checkout
Approve below and you go straight to secure checkout with Stripe. I send the intake and your invoice the same day, and we run session one inside ten working days.
Secure payment handled by Stripe. Card details never reach Mission Relearn.
Prefer an invoice with a 14 day term, or want to talk it through first? Reply to my email or write to annet@missionrelearn.com.
08 · The small print
You are buying as a private individual, so you get consumer protection. Here it is in plain terms.
You can cancel within 14 days of paying and get your money back. If you ask me to run session one inside those 14 days and then decide to stop, I only charge for what I have already delivered and refund the rest.
Move any session up to 24 hours ahead at no cost. Life happens and I would rather move a session than have you sit through one badly. Sessions run online, 1:1, in English.
Email me and I will fix it. If we cannot resolve it between us, you can take it to the EU online dispute resolution platform at ec.europa.eu/consumers/odr.
Who you are buying from. Mission Relearn, a Dutch sole proprietorship owned by Annet Kloprogge. Jaarbeursplein 6, 3521 AL Utrecht, Netherlands. KVK 99384949 · VAT NL005382931B53 · annet@missionrelearn.com · +31 6 1128 7885. Payment is handled by Stripe; your card details never reach Mission Relearn.