Inbound inquiries
New requests need source, fit notes, owner, reply due date, value band, next action, and stale-lead review.
Request inquiry intake queue
Freelancers and consultants
Keep inquiries, qualification, proposal follow-up, invoice status, and delivery handoff in one queue.
For independent operators and small consultancies where valuable requests arrive through referrals, email, forms, LinkedIn, calls, or partner introductions but the next action still depends on memory.
Consulting bottlenecks
Start where client intent stops being visible.
Proposal follow-up
Sent proposals need scope version, decision owner, follow-up date, objection notes, close reason, and handoff status.
Request proposal follow-up queueInvoice status
Accepted consulting work needs invoice status, payment-instruction review, receipt evidence, start condition, and owner review.
Request invoice status queueDelivery handoff
Approved work needs accepted scope, required inputs, access boundary, due date, delivery proof, client confirmation, and follow-up.
Request delivery handoff queueFirst build scope
- One pipeline for inquiries, qualification, proposal follow-up, invoice status, accepted scope, and delivery handoff.
- Fields for source, client fit, value band, owner, status, next action, due date, and close reason.
- Proposal fields for sent date, scope version, decision owner, follow-up date, objection note, and outcome.
- Invoice/payment handoff fields for accepted scope, instruction review, receipt status, and delivery-start condition.
- Delivery fields for required inputs, access boundary, proof, client confirmation, follow-up date, and daily review notes.
Safe boundaries
No proposal, contract, invoice, payment instruction, BTC address, delivery start, access request, client contact, platform action, or money movement is created automatically.
No passwords, wallet seeds, private keys, exchange credentials, client secrets, platform credentials, or payment processor secrets are requested by this page.