AI Opportunity Assessment
Know what to automate first, and what it will take.
Leave with the one workflow to automate first, what it should give back in hours a week, and a costed plan to build it, or a clear reason not to. A 30-minute conversation with Kelvin Tran, then a short written brief you keep.
What you get
A Workflow Teardown, and the brief around it.
Useful on its own, whether or not you hire us.
- A Workflow Teardown of the first one: the click path your team follows today next to the automated path, with your hours a week beside it
- A short intake about your business, your tools and the main workflow problem
- A focused conversation of about 30 minutes, by video call
- A concise written brief with up to three prioritized opportunities
- What can be configured, what needs development, and what is still uncertain
- Indicative effort and economic scenarios, only where your numbers support them, with the inputs shown
- A proposed next step, which may be "keep your current tool" or "don't build this"
What it is not
No surprises later.
- Not a production integration, a custom application or a working prototype
- Not a full technical architecture or a compliance certification
- No access to your business accounts and no import of customer data
- No guaranteed savings, revenue or delivery dates
- Not unlimited consulting: one round of clarification questions by email is included
We may show you an existing demonstration where it is relevant. A new prototype is only built inside a separately scoped and priced project.
Who qualifies
Four plain criteria.
- You run an operating business that currently serves customers.
- You have a recurring workflow (customers, scheduling, follow-up, operations or content) you want to reduce or improve.
- You are the owner, or you are authorized to discuss that workflow.
- You can describe the tools you use and how the work is done today.
One assessment per business. If a request does not meet these criteria, we tell you, and where we can, point you to a better option.
How it works
From request to brief.
- Request. Tell us about the workflow below. This is a request, not a booking.
- Review. Kelvin reviews it within 2 business days and emails you either a link to choose a time or a short reply explaining why it is not a fit.
- Conversation. About 30 minutes on a video call. Qualified requests are scheduled in the order received; if there is a wait, we tell you the expected date first.
- Brief. Delivered within 5 business days after the conversation.
- Your call. If you want to go further, we send a written implementation proposal. If not, the brief is yours to keep.
Request
Tell us about the workflow.
Five fields, about two minutes. Everything else is optional, and "not sure" is always a fine answer.
Before you send
Please do not include passwords, payment details, or patient or customer personal information. We never ask for them at this stage.
A request is not an appointment. You will get a scheduling link by email if it is a fit.
Have a defined project with a clear scope? Choose "I have a defined project" in the form and we will route it as a project inquiry instead.
Before you ask
Is this a sales call?
No. You get a written brief you can use without us, and the brief may recommend keeping your current tools or not building anything. If you want an implementation proposal afterwards, you ask for it.
What happens after the deadline?
Requests submitted by October 18, 2026, 11:59 PM Arizona time keep the launch terms, even if the conversation happens later. After that, you can still request an assessment; we confirm the scope and any fee with you before anything starts. Nothing is ever charged automatically.
What if my software cannot connect to anything?
Then the brief says so. Some tools allow reading data, some allow writing, some allow neither. We check your specific tools and recommend what is practical, including not connecting at all.
How much does implementation cost?
It depends on the workflow, the tools and what needs building, so it is scoped and priced per project in writing. The brief gives indicative effort where your inputs support it.