Industry paths

Start from the business type, then scope one revenue workflow.

Use these paths when the bottleneck is concrete: requests arrive, quotes need follow-up, invoice/payment status is unclear, or delivery handoff depends on memory.

Start general industry intake

Local service businesses

Service requests, quotes, invoice/payment status, and delivery proof in one owner-reviewed queue.

View industry page Request local service workflow

Small ecommerce teams

Product questions, high-intent leads, invoice exceptions, fulfillment notes, and post-purchase follow-up.

View industry page Request ecommerce workflow

Freelancers and consultants

Inbound requests, qualification, proposal follow-up, invoice status, accepted scope, and delivery handoff.

View industry page Request consultant workflow

Founders with manual sales work

Founder-owned replies, quote changes, approval notes, payment status, delivery start, and weekly review.

View industry page Request founder workflow

Fixed-scope first

Expected deliverable: one queue or operating map, not a platform migration.

Each path still needs owner review before any customer reply, proposal, contract, invoice, BTC instruction, delivery start, access request, or payment request.

Review engagement bands

Use this when

Requests arrive in more than one place.
Follow-up depends on memory.
Accepted work lacks a delivery-start condition.
Invoice/payment status is separate from delivery notes.
The owner needs one daily review queue.

Boundaries

No outreach, publication, profile submission, account creation, customer contact, contract, invoice, BTC instruction, payment request, delivery start, access request, or money movement is created by this page.

No passwords, wallet seeds, private keys, exchange credentials, or customer secrets are requested.