Loading
Skip to content
ZeptazHow it works

From fit call to managed plan.

A deliberate, low-friction path. The delivery clock only starts at Access Lock, once access, test data, routing rules, and owners are confirmed.

01 / How it works

From fit call to managed plan.

A deliberate, low-friction path. The delivery clock only starts at Access Lock - once access, test data, routing rules, and owners are confirmed.

  1. 01

    Workflow Fit Call

    30-45 minutes

    A short, low-friction conversation to see how inquiries move from form/inbox to an owner and a follow-up.

  2. 02

    Diagnostic

    3-5 business days

    We map your current flow, name the top leak points, and recommend a founding build scope.

  3. 03

    Access Lock

    GATE

    Driven by your side - typically under a week · CLOCK STARTS HERE

    The readiness gate. Access, test data, routing rules, and owners are confirmed before the clock starts.

  4. 04

    Build

    Per package - 10 business days to 6 weeks

    We build the reusable workflow engine against approved test data - connector-first, modular.

  5. 05

    UAT

    3-5 business days

    You test agreed pass/fail scenarios. Feedback is consolidated into one punch list, then fixed.

  6. 06

    Handover

    One session

    Runbook, workflow map, limitations, and responsibilities reviewed. The build phase ends formally.

  7. 07

    Managed Plan

    Monthly - cancel anytime

    Optional ongoing plan with hour-capped support, monitoring, and change requests.

02 / The fine print

What each step actually asks of you.

No mystery phases. For every step: what we need from your side, what lands on ours, and how long it takes.

01

Workflow Fit Call

> intake.scan(form, inbox) · > trace: inquiry → owner → follow-up · ready: discovery
You bring

30 minutes and honest answers about how inquiries move today.

We deliver

A straight read on whether automation helps - and a clear no if it doesn’t.

Duration

30-45 minutes

02

Diagnostic

> flow.map(current) · > detect: leak-points · > scope.recommend(founding build)
You bring

A walkthrough of your tools and a few real (redacted) inquiry examples.

We deliver

A 1-3 page flow map, the top leak points, and a recommended scope with a price range.

Duration

3-5 business days

03

Access Lock

> access.confirm · > test-data.verify · > routing.rules.lock · clock: START
You bring

Scoped access, test data, routing rules, and named owners - confirmed.

We deliver

A readiness checklist signed off by both sides. The delivery clock starts here.

Duration

Driven by your side - typically under a week

04

Build

> engine.build(modular) · > connectors.attach · > test-data.bind
You bring

Availability for quick clarification questions - not a meeting marathon.

We deliver

The workflow engine built connector-first against approved test data, with logs.

Duration

Per package - 10 business days to 6 weeks

05

UAT

> scenarios.run(pass/fail) · > feedback → punch-list · > fixes.apply
You bring

Run the agreed pass/fail scenarios against your real cases.

We deliver

One consolidated punch list and the fixes - not an endless revision loop.

Duration

3-5 business days

06

Handover

> runbook.deliver · > workflow-map.review · build-phase: CLOSED
You bring

One session with the people who will own the system day to day.

We deliver

Runbook, workflow map, known limitations, and named responsibilities - formally closed.

Duration

One session

07

Managed Plan

> monitoring.enable · > support.cap(hours) · change-requests: OPEN
You bring

Nothing - it’s optional. Choose it if you want us on call.

We deliver

Hour-capped support, monitoring, and change requests under a monthly cap.

Duration

Monthly - cancel anytime

03 / Trust & security

Built to be safe inside your stack.

We treat candidate, client, and operational data carefully. AI is an assistant inside a controlled workflow - not an autonomous actor. The fastest way to show it is our own access log - note what gets denied.

$ zeptaz access --audit
01request: full CRM/ATS export
DENIED
Minimum access

We request only the candidate, client, and job data the approved workflow needs.

02request: raw password share
DENIED
No raw passwords

Invitations, OAuth, restricted API keys, or client-owned accounts only.

03request: live PII for build
DENIED
Anonymized test data

Logic is engineered on anonymized or representative test data where possible.

04request: ai.send(unreviewed)
DENIED
Human-approved AI

AI drafts and sensitive outputs are prepared for human review and approval.

05request: scoped workflow access [approved-by: you]
GRANTED
The only access we take

Exactly the scope confirmed at Access Lock - reviewed with you, revocable by you.

ok · least-privilege by default - the system can’t leak what it never had
Get started

Start with a fit call.

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.