Get inquiries owned and followed up.
Get started- TIMELINE
- 10 business days once access is set up
- Intake & ATS/CRM update
- Required field check
- Owner assignment
- Team alert
- Basic follow-up task
ZeptazPricing
Sized builds, priced after proof.
Pick the scope, not the loose parts. Every package is the same connected engine, just more modules and reach. Final pricing follows the founding diagnostic.
01 / Packages
Three sizes. Start with one workflow or connect them all.
Every package comes with a clear scope and timeline. We confirm the price after mapping your setup, so you know the number before you commit.
Add AI drafts and stale-inquiry logic.
Get started- TIMELINE
- 2-3 weeks once access is set up
- Everything in Starter
- AI response drafts (human-approved)
- Stale-inquiry alerts
- Richer follow-up logic
- Stronger logs
A multi-workflow operations system.
Get started- TIMELINE
- 4-6 weeks once access is set up
- Everything in Growth
- Multi-workflow across intake & follow-up
- Handoff & reporting
- Operations dashboards
- Connector layer per system
Final pricing depends on workflow complexity, ATS/CRM access, connector availability, data quality, AI involvement, module count, and support needs. Timelines begin once access, test data and owners are confirmed.
02 / Build manifest
Exactly which modules each build ships.
Every tier runs the same connected route - bigger builds switch on more stations. Nothing here is a bolt-on; the order is the dependency chain.
$ zeptaz build --manifest
moduleSTARTERGROWTHSCALE
01intake- Inquiry Intake
■■■02record- ATS / CRM Record
■■■03field_check- Field Check
■■■04categorize- Categorization
■■■05owner- Owner Assignment
■■■06alert- Team Alert
■■■07draft- AI Response Draft[human]
·■■08followup- Follow-up Task
■■■09stale- Stale-Inquiry Flag[alert]
·■■10handoff- Placement Handoff
··■11reporting- Reporting
··■01Inquiry Intake
■ STARTER■ GROWTH■ SCALE
02ATS / CRM Record
■ STARTER■ GROWTH■ SCALE
03Field Check
■ STARTER■ GROWTH■ SCALE
04Categorization
■ STARTER■ GROWTH■ SCALE
05Owner Assignment
■ STARTER■ GROWTH■ SCALE
06Team Alert
■ STARTER■ GROWTH■ SCALE
07AI Response Draft[human]
· STARTER■ GROWTH■ SCALE
08Follow-up Task
■ STARTER■ GROWTH■ SCALE
09Stale-Inquiry Flag[alert]
· STARTER■ GROWTH■ SCALE
10Placement Handoff
· STARTER· GROWTH■ SCALE
11Reporting
· STARTER· GROWTH■ SCALE
ok · tiers set reach, not composition - load-bearing stations can’t be removed
03 / How engagements run
Fixed scope, formal handover, optional support.
Every build follows the same shape: scoped after the diagnostic, clocked from Access Lock, closed with a formal handover. No open-ended retainer disguised as a project.
- 01Timeline
- Starts at Access Lock, never at contract signature. Starter lands in 10 business days; Growth in 2-3 weeks; Scale in 4-6 weeks.
- 02Scoping
- The founding diagnostic produces the scope, timeline, and price range. You approve the number before the build starts - no surprise line items mid-project.
- 03Handover
- Runbook, workflow map, known limitations, and named responsibilities - reviewed together in one session. The build phase closes formally.
- 04Ownership
- The workflows run in your accounts on your tools. Walk away after handover and everything keeps working - and stays yours.
- 05Support
- The optional Managed Plan adds hour-capped support, monitoring, and change requests on a monthly basis. It is not required to keep the system running.
- 06Changes
- In-build changes go through the UAT punch list. Post-handover changes run through the Managed Plan or a scoped mini-build.
Final pricing depends on workflow complexity, ATS/CRM access, connector availability, data quality, AI involvement, module count, and support needs. Timelines begin once access, test data and owners are confirmed.
04 / FAQ
Common questions.
Straight answers on scope, data, and how the work runs. Still unsure? A fit call sorts it fast.
After Access Lock is complete - once access, test data, routing rules, and owners are confirmed.
Workflow complexity, ATS/CRM access, connector availability, data quality, AI involvement, module count, and support needs. The founding diagnostic pins the number before you commit.
No. The build ends formally at Handover with a runbook and workflow map. The Managed Plan is an optional monthly, hour-capped add-on for monitoring and change requests.
Yes - that’s the point of the tiers. Starter, Growth, and Scale are the same engine at different reach, so upgrading adds modules without rebuilding what you have.
Get started
Get a build scope and price.
Book a workflow fit call. We look at how inquiries move from form and inbox to an owner and a follow-up, and where work is leaking today.