Our own workflow · Interactive demonstration
A brief shouldn't disappear into an inbox
Our enquiry workflow gives the sender a receipt and a private page showing whether the studio has started looking. The studio still decides what to take on.
Follow a sample enquiry
These controls simulate the status page. They don't send an enquiry, an email or any personal data.
Sample private status page
Received
Your brief was received and is waiting for review.
- Reference
- DEMO-001 · sample only
- What happens now
- A receipt is prepared with a private link. The brief joins the studio's review queue.
The human decision
Sending the brief doesn't agree a scope, price or delivery date.
The wording above follows the implemented status page. Your real link shows your enquiry's current state; it doesn't reveal the brief or uploaded documents.
The task
Give a prospective client something more useful than “message sent”, and give the studio a way to track the next step without copying the brief between tools.
The constraint
An enquiry isn't a client account. A status link should show progress without disclosing the brief, attachments or anyone else's work.
An engineering decision
The receipt links to a temporary, revocable status page. It shows a small set of human-readable states. Qualifying the request, agreeing the work and granting workspace access remain separate steps.
What it does today
The application records the enquiry, queues its receipt and exposes the current status through the private link. A studio member can move the enquiry through review and follow-up. The demonstration above uses sample data and never touches that queue.
This is a demonstration of our implemented workflow, not a report of client results. Delivery of real email depends on the configured provider; the local preview keeps mail in its development inbox. We have not claimed a time saving or response-time guarantee.