After the working session · designs included
I listen. Then I write something you can decide from.
This page shows the shape of that artifact. Each section below explains what I put there in a real engagement, then shows an example fill-in so you can see the level of thought. Yours would be written from what we discuss.
What a proposal is for
One clear next decision
The fill-in is an example
This sample exists so you can see the craft and the designs.
How to read this
The structure is what I reuse. The words would be yours.
A real proposal is written after a working session. I write back what I heard, rank a few moves, and show designs of the workflows that matter so you can keep, cut, or change them. Below, each block has two layers: what that section is for, then an example of how it might read.
01
What I heard
Your bottlenecks, in your language, written from the conversation.
02
What I recommend
A short ranked list. Enough to decide what to size.
03
Designs
Click-through pictures of what I would build. The example here is Desk.
What this section is for
Every real proposal opens with a 30-second decision. Three columns: what I heard, what I recommend, what happens next. You should be able to stop here and know the ask.
Example fill-in
What you would be asked to decide
What I heard
- The week is full of repeat assembly.
- The good answer lives in someone’s head.
- Numbers exist. The decision page does not.
- Exceptions eat more time than the plan.
What I recommend
- A desk for inbound: draft from what already worked. You still send.
- A weekly brief: what moved, what to change.
- Start from winners: rebuild less from memory.
What happens next
- You pick what (if anything) to size
- I return scope, timeline, and investment
- Nothing is built until you approve
What this section is for
After we talk, I write back what I heard. This is the part people recognize themselves in. If I missed something, we fix it before anyone talks about software.
Example fill-in
The kind of thing that lands here
Repeat work is assembled by hand
The same deck, the same reply, the same setup. Once the page exists the call is usually obvious. Getting to the page is the job.
The good answer is tribal
Questions land in email and chat. The reply that worked last month lives with one person. There is no desk that drafts from protocol and waits for a human to send.
Data without a decision
The numbers are somewhere. Monday still starts with rebuilding the story. I bring a data habit here: look at what you actually ran, then adjust.
Exceptions run the day
The plan is fine until the odd case arrives. Those cases still need a person on send.
What this section is for
This is where I rank a few moves. In a real proposal they come from the session. The examples below are the kinds of recommendations I make when the conversation points that way.
Example recommendations
Three kinds of moves, ranked after we talk.
01
A desk for inbound
Most shops have customer or client questions. Draft from what already worked. A person still sends.
02
A weekly brief
What moved. What to change. One page someone can stand behind.
03
Start from winners
Name the offer. Draft from templates and past results. A person still launches.
What this section is for
This is the lever. After I listen, I show the system. You click through screens, keep what is useful, and drop the rest. A real proposal would use your language. The example here is Desk, because almost every business has inbound questions that still need a human to send.
Example design · Desk
You would click through something this considered
Mail in. Order matched. A draft written from what already worked. You still send. Resolutions that work become protocol. That is Desk. Open the design page and walk inbox, review, knowledge, and analytics. Nothing sends.
Peek · fictional sample shop
Desk · inbox, review, knowledge
Open full designNeeds review · 4
Maya Chen
Where is order #1842?
Jonah Reed
Wrong item in the box
Elena Cho
Board arrived cracked
Priya Shah
Do you wholesale the linen set?
What this section is for
I say how the engagement works so the path is obvious: session, recap, this kind of page, then you choose.
Listen first. Then make the next decision easy.
- 1
Working session
I listen to how the business runs, where the week gets stuck, and how work already moves. No canned itinerary.
- 2
Written recap
Top opportunities, what I would defer, and suggested next steps. Enough to decide if a larger piece of work is worth it.
- 3
This kind of proposal
What I heard, ranked recommendations, and designs you can click. Built from the session, in your language.
- 4
You decide
Nothing is built until you approve a scope. The sample you are reading stops here on purpose.
Who writes this
Jonathan Evans · Author29
I listen, then I turn what I heard into tools people can use. Seven years across industries. A background in data analytics and data science. I ran an e-commerce business. The rest is how that shows up in the work.
Listening
I hear how the week actually runs, then write it back in your language so we can decide from the same picture.
Speed
What I hear becomes a design and a working system quickly. The sample on this page is the pace.
Design thinking
I think from the owner’s seat and from the person who will use the thing. If it is not valuable on Monday, it is not done.
Communication
Clear, personable, easy to work with. People mention it often.
AI engineering
Agents and applications that hold up. Durable loops, human review where judgment belongs, evals from the start.
Data and systems
Seven years across industries. Data analytics and data science, plus engineering that treats access, security, and longevity as part of the build.
Aesthetic eye
The tool should look like it belongs in the business. Craft is part of whether people will actually use it.
Owner’s perspective
I ran an e-commerce business. I still design as someone who has to live with the system after the meeting ends.
What this section is for
A real proposal ends with one ask. Book the session, or sit with the recap. This sample ends by pointing you back to that conversation.
Yours would be written from what we discuss
We talk. I listen. I send a short recap. If that is useful, I write a proposal at this level of detail, with your name on it and designs that match your workflows. Click the Desk design if you want to see how deep that part goes.