Door 3 of 3 — Ship
The Solution Build. We ship it. Train your team. Hand over the runbook.
We build it, deploy it into the tools you already use, train your team, and hand over a runbook anyone can troubleshoot.
Sample runbook page · 6 pages total
A working automation, not a deck of recommendations.
Build is the only tier where you get something running in production at the end. Plan stops at the doc. Build keeps going until the workflow is live, your team is trained, and the runbook hands over.
- 01
Live, working automation
Built end-to-end on Claude, ChatGPT, Codex, Zapier, n8n, or Make — whatever fits the workflow. Wired into the tools you already use.
- 02
Integration with your existing stack
Email, sheets, CRM, docs, accounting — we plug into what you have. No new admin panel for your team to learn unless one is genuinely required.
- 03
30-minute live training
Recorded Zoom for whoever runs the workflow. We answer real questions on real data, not a demo dataset.
- 04
6-page runbook
Live-status panel, when-X-happens troubleshooting table, escalation paths, rollback steps. Anyone on your team can fix the workflow at 10pm without us.
- 05
30 days of email support
Anything breaks in the first month, we fix it. No ticketing system, no SLA games — direct email to support@vireonailabs.com.
- 06
Optional monthly tune-up retainer
Some clients want eval refreshes, new prompts, or new integrations after launch. Available, never required. Your runbook is enough on its own.
2–4 weeks. Daily check-ins. One handoff.
20-min Zoom. We confirm fit, agree on success criteria, send a one-page proposal.
We start the build the day you sign. Slack channel opened for daily check-ins.
We run the workflow on your real data with eval cases. Failures fixed before you see them.
30-min recorded training. Runbook delivered. Workflow flips to your team.
Anything breaks, we fix it. No ticket queue. Engagement closes after 30 days.
Owners who want the working automation handed back, not a deck of recommendations. Best when your team's time is worth more than the gap between Plan and Build.
- Everything in the Implementation Plan, executed
- Built end-to-end on Claude, ChatGPT, Codex, Zapier, n8n, or Make
- Wired into your existing email, sheets, CRM, and docs — no new platform to learn
- 30-minute live training for whoever runs the workflow
- 6-page runbook: live-status panel, when-X-happens table, rollback steps
- 30 days of email support after launch — anything breaks, we fix it
- Optional monthly tune-up retainer (never required)
What this isn’t
The Build ends at handoff + 30 days. By design.
- Build is not ongoing maintenance. After 30 days the engagement is closed.
- Build is not a SaaS product we keep hosting on your behalf — you own the workflow and the credentials.
- Build is not unlimited revisions. We agree on success criteria upfront and ship to that bar.
- Build is not a multi-workflow rollout. Multiple workflows are a custom quote, not the catalog.
- Build is not a substitute for an internal product team — for net-new internal tools, talk to us about scope.
Five questions every owner asks before scoping a Build.
Is the price really fixed?
Yes. After the free 20-min scoping call we send a one-page proposal with a fixed dollar number, the deliverables, and the timeline. If scope changes mid-build, we re-quote in writing before doing the work. We do not invoice for hours we didn't agree to.
Why $300–$750? What lands at the high end?
Floor ($300) is a single-workflow automation with one or two integrations and existing tools. Top ($750) is a workflow with 4+ integrations, a custom review queue, and edge-case handling. We don't take builds outside this range from the catalog — those go through the custom-quote path.
What if we don't have an audit or plan first?
Plenty of clients come straight to Build. The free 20-min scoping call replaces the audit for tightly-scoped work. If we discover the workflow is bigger than it looked, we'll tell you on the call and recommend the Plan tier instead.
What happens if our team can't run it after handoff?
The runbook is written for a non-technical operator — it has a status panel, a when-X-happens table, and rollback steps. The 30 days of email support covers training gaps. If after 30 days you want occasional help, the optional tune-up retainer is there. Most clients don't take it.
Will you maintain it forever?
No, and that's intentional. We hand you a working automation, a runbook, and the keys. After 30 days you own it outright. The optional retainer exists for clients who want monthly eval refreshes or new integrations — but we don't bake that into the Build price because most workflows don't need it.
Have us ship it for you.
Free 20-minute scoping call. Fixed price after. 2–4 weeks to a working automation, trained team, and a runbook.