Direct answers.

Most fit calls happen within the week. Audits typically kick off within seven days of a signed scope. Pilot builds usually start within two weeks of the audit. The bottleneck is almost always your team's calendar, not ours — the discovery call and the walk-the-work session need real attention from someone on your side.

No. Every workflow we build keeps a human in the review loop on anything customer-facing — quotes, proposals, follow-ups, marketing. The system drafts and prepares; your team reviews and sends. The point is to remove the prep work, not the judgment. The time freed up is meant to go back into the higher-judgment work that was getting crowded out.

No. We build around the tools you already use. If something would genuinely help, we tell you and explain why. We don't resell software, we don't have referral relationships with vendors, and we're not paid to recommend any particular tool. The build is in your tools, owned by you, with you holding every account.

That's what the audit is for. We watch the work, surface the bottlenecks, and rank what's worth fixing first. Most operators have a hunch about where time is leaking; the audit tests the hunch and either confirms it or finds a bigger leak somewhere else. The output is a written diagnosis, not a sales pitch.

Weekly written Monday updates and two milestone demos per build. No constant chat noise. The Monday update covers what shipped, what's next, and where we need a decision. The milestone demos are scheduled, not surprise drop-ins. Email or Slack for ad-hoc questions, with a one-business-day reply standard.

Priced privately after the fit call. We keep pricing off the public site on purpose — every workflow is different, and we'd rather scope it right than anchor low. The audit fee is credited against the pilot build if you decide to move forward. Fit calls are designed to end with a written scope and a price within two business days.

You get a written diagnosis, a ranked list of three to five automation candidates, and a recommended pilot scope and price. From there, you can move into a Pilot Build, sit on the document and revisit later, or take it and have someone else build it — the audit deliverable is yours either way. The engagement path is designed to flow from Audit to Pilot, but every stage is a stop point if it should be.

Yes. We sign your NDA if you have one, or use a simple mutual NDA if you don't. The audit and any build work touch real workflow data — customer lists, pricing, quotes, internal documents — and that's a normal expectation. We are not in the business of sharing engagement details for marketing without explicit written permission.

We follow the principle of least access — your accounts, your data, scoped permissions. Where AI models are involved, we use providers that do not train on your data by default (Anthropic, OpenAI enterprise endpoints, or model deployments inside your own environment when the use case calls for it). We do not store your data in our systems beyond what's needed to operate the workflow.

Make or n8n for orchestration. Anthropic Claude or OpenAI for the model layer. Airtable, Google Sheets, or your existing CRM and ERP for data. Resend, Postmark, or your existing transactional email provider for sends. Slack or Teams for internal interfaces. We pick based on what you're already running, not what we prefer.

You do. The audit gives you a ranked list with effort, ROI, and risk for each candidate. The conversation about what to build first is a conversation, not a recommendation we hand down. Our job is to make the trade-offs visible. Your job is to know which trade-offs are worth making in your business.

Two answers. First, we build with monitoring and alerting on the parts that can break silently — failed runs, missed sends, drift in the source data. Second, the Operations Retainer exists for this — monthly tuning catches the slow drift before it costs you. Workflows decay; the retainer keeps them honest. Cancel any month.