One bounded business workflow
Process map.
Starting brief.
Bring the work you want to improve. We map how it should run and define a useful first version to build.
€199 · 60 minutes · process map and starting brief within two business days
Book my session ↗Explore the sample package ↓03 / Something you can take forward
Your process map.
Your starting brief.
A concrete package for one workflow, ready to discuss with a developer or use with your development assistant.
One process.
A clear starting point.
- Before we meetYou share the process, an example input and the result you want.
- 60 minutes togetherWe map the work, choose the boundaries and agree a useful first version.
- Within 2 business daysYou receive the edited map and starting brief, including assumptions and open questions. One follow-up clarification by email is included.
Designed for one bounded workflow. Software development, integration testing and a complete technical architecture are separate work.
Book my sessionChoose a time and pay securely through Cal.com. Privacy
Not sure this session fits? Email me.
A few sentences about the process you want to improve are enough.victor@victorlipov.comFrom enquiry to approved quote
Starts with an incoming request. Ends when an approved quote has been delivered and recorded.
Incomplete requests wait for clarification. Failed AI extraction goes to manual entry. Nothing reaches the customer without approval.
A first build with clear boundaries
The brief connects the process to the interfaces, data and checks needed to start development.
- Entry point
- A simple intake form and manual email paste.
- First interface
- A queue with request details, extracted facts and an approval screen.
- AI boundary
- Extract a draft with references to the original text. No authority over prices or sending.
- Delivery route
- Versioned PDF and email, released by an explicit approval.
- First build
- Prove the manual path with sample data, then add AI extraction.
“Read the process map and this brief. Identify the unknowns that block a first build. Implement the manual intake-to-approval path first...”
The next person can pick it up.
A small foundation for continuity, useful whether the next contributor is a developer or an AI assistant.
- Keep decisions
- Record the chosen scope, the reason and the assumptions still to check.
- Save the state
- What works, what was tested, what is blocked and the next useful action.
- Name ownership
- A person approves customer promises. Development agents work within the agreed scope.
- Leave evidence
- Link to the source files and checks so the next contributor can verify the handoff.
A readable handoff is enough for this sample. An installed multi-agent system is outside the session package.
Is this the right next step?
Bring a process
you know from the inside.
For owners and operators who can show how the work happens today, and want a practical starting point for improving it.
Can I cancel?
You can cancel and receive a refund up to two business days before the session.
What should I bring?
One recurring workflow, an anonymised example of what comes in, and an example of the result you want. Screenshots or existing documents help. A polished specification is unnecessary.
What if AI is not useful for my process?
The map can recommend ordinary software or a simpler process change. We will make that choice explicit in the brief.
Can I build it myself with an AI assistant?
The starting prompt gives your assistant context, scope and acceptance checks. You will still need to review its work. The package is a starting point for development, not a guarantee of a finished application.
What if my idea is too large for one session?
We choose one useful workflow before the session. The package covers that slice and records the larger questions separately.
Can you build the system afterwards?
Yes, implementation can be discussed separately. You can also take the package to another developer.