The questions buyers actually ask.

Under 24 hours from signup. The Discovery phase (Apify scrape + market research dossier) runs immediately; Synth and Live ship overnight. The first receipt — landing page on a real subdomain with a verified diff — lands the next morning.

Commands run, exit codes, the file diff, spend in USD, model + token counts, the Verifier score (1–5), and any artifacts the task produced. The URL is public-by-default with a revocable share token — you can show an investor or a customer the proof without a screen-share, and you can revoke the link at any time.

An independent agent that scores every task 1–5 before it counts as shipped. The same agent that ran the task does not get to declare it done. The score lands in the receipt; failed verifications roll the task back and refund the credits.

• First cycle ships under 24 hours after signup.
• Engineering tasks: under 6 hours from approval to receipt with a verified diff.
• Failed tasks auto-refund credits within the same cycle.
• ZIP export downloadable within 10 seconds of request.
• Live platform status, including every upstream dependency, on /status.

Per-organisation Stripe subscription with monthly plans (Free / Founder / Scale / Enterprise). Each plan grants a monthly credit budget; you can top up at any time with Stripe Checkout credit packs. Per-agent budget caps in USD prevent runaway spend, and failed tasks auto-refund credits within the same cycle. See /pricing for tier details and credit pack prices.

Yes — once team invites land in Pillar 6B, your settings page will have a Team tab with role-based invites (owner / admin / member / viewer). Invites are sent by email via Resend with a revocable token; accepting the invite writes the teammate into your org_memberships and they see the same workspace.

Only if you connect Stripe. The Finance Autopilot agent uses a Stripe Connect Express OAuth so tokens stay scoped and revocable. We never store your raw secret keys — the connection lives in Stripe; we hold an account-level reference. Disconnecting at any time is one click and stops every downstream agent from reading your numbers.

One-click ZIP export of everything you own — audit log, every document as Markdown, sandbox sessions, Slack deliveries, learned skills. Closed source as a SaaS, open source on the way out: the export is the unlock.

Slack (primary, native Block Kit), Microsoft Teams (Bolt-JS adapter), and email (Resend, with inbound webhook for reply-to-thread routing). WhatsApp, iMessage, and SMS are on the roadmap (v1.1). External posts are gated by an approval card; the founder remains in the loop unless autonomy is explicitly raised.

Three layers. (1) Sibling kigya products — outserp (SEO), reelgrow (short-form video), hanbai (newsletter) — native API wrappers. (2) 3,000+ tools via Pipedream Connect with managed OAuth; tokens stay in Pipedream’s vault. (3) Stripe Connect Express for the customer’s company finance data and GitHub/GitLab for repo activity feeding the Engineering agent.

Yes — the Engineering agent runs a Plan → Patch → Test → Ship loop in an isolated Linux sandbox (E2B). The final git diffand test output land in the receipt before the deliverable posts. This is the wedge over Viktor (orchestrates tools but doesn’t ship code) and Revnu (growth-only).

Every cycle produces a distilled cycle_learningsrecord. Phase-aware retrieval surfaces what worked for similar-niche companies into the prompt of the current run. Your first cycle inherits the learning of every prior cycle across every prior tenant — the cross-niche skills library is the moat.