Discovery call
A short first call to understand fit, urgency, and whether the work is an audit or a build.
EMVYClient journey
What happens after the first call.
The standard path is discovery call, decision email, payment, audit or build deep-dive, findings review, build kickoff, implementation, and maintenance.
Standard flow
A clear path from first conversation to monthly support.
This is the standard EMVY engagement flow for now, before the whole thing is automated.
Decision email
Send a concise follow-up with the recommended path, scope summary, and a payment link or invoice.
EMVYAudit or build deposit
Collect payment before detailed work begins. Audits are paid up front; builds are paid by milestone or deposit.
ClientAudit deep-dive call
Run a structured call to gather workflow detail, constraints, systems, people, and edge cases.
EMVY + clientAudit review pack
Turn the notes into a clean, presentable audit deliverable that highlights opportunities and recommendations.
EMVYFindings call
Present the audit findings, answer questions, and agree the build or implementation path.
EMVY + clientBuild proposal and payment
Confirm the implementation scope, pricing, timeline, and payment structure before build work starts.
EMVY + clientBuild kickoff
Use the audit outputs to start the build, set milestones, and create the working system.
EMVYDemo and feedback
Review the build with the client, capture amendments, and agree the next changes.
EMVY + clientImplementation assistance
Make revisions, support adoption, and help the team actually use the system in daily work.
EMVYMaintenance plan
Move the client onto a monthly maintenance or support arrangement for ongoing changes and oversight.
EMVYPayment standard
The standard is a simple scope summary plus a payment link or invoice.
For audit work, collect payment before detailed work begins. For builds, collect a deposit or milestone payment before kickoff, then continue on staged payments if the scope is larger.
Collect payment before detailed audit work begins.
Use clear wording, an explicit scope, and a deadline so the handoff is frictionless.
Send a simple scope summary + payment link or invoice after the discovery call.
Use clear wording, an explicit scope, and a deadline so the handoff is frictionless.
Use milestone or deposit payments for builds before kickoff.
Use clear wording, an explicit scope, and a deadline so the handoff is frictionless.
Invoice maintenance monthly in advance.
Use clear wording, an explicit scope, and a deadline so the handoff is frictionless.
Call questions
The questions we should ask on audit and build calls.
These sets can later be handled by an agent, but they should be human-led now so we capture the right detail from the start.
Questions to uncover how the business really works before creating the audit report.
- What is the business trying to improve right now?
- Where does the current workflow slow down or break?
- What tools, inboxes, forms, spreadsheets, or CRMs are already in use?
- Who owns each step and where do handoffs get lost?
- What happens when something goes wrong or sits unanswered?
- What would a successful audit need to show the client?
Questions to define scope, delivery, risk, and implementation details before the build starts.
- What exact system or workflow are we building?
- What does success look like in the first 30 days?
- What must be automated versus kept manual?
- What systems need to integrate or share data?
- What are the approval, security, or permissions requirements?
- What does the handover and maintenance plan need to include?
Documentation
Every meeting should produce notes, actions, and a usable client summary.
Why this order matters
Paying before detailed work protects time and keeps the engagement serious.
Documented meetings
Every call should create structured notes, action items, and a client summary.
Future automation
Later, an agent can take notes live and draft the outputs for review.
No loose ends
Each step ends with a decision, a deliverable, or a next scheduled action.
Meeting note flowjoin the call with a structured note template · capture goals, pain points, tools, and edge cases · tag action items, open questions, and follow-up owners · generate a client-ready summary after the meeting · feed the notes into audit, build, and maintenance tasks
End state
Discovery becomes audit, audit becomes build, build becomes support.
That is the operating pattern we can now automate step by step with Hermes and meeting agents later.