Requests

A request is a single unit of work — a fix, a feature, a content update, an integration. Most engagements are managed as a stream of requests rather than one giant scope document.

Submitting a request

From the dashboard or the Requests tab, click New request and fill in:

• Title — short summary (Fix nav overlap on iPhone, not Bug)
• Description — what you want, what's happening today, and any links or context. The more upfront, the faster we move
• Page URL (optional) — direct link to the page in question
• How you're feeling about this — pick a sentiment from "All good — no rush" to "Very worried — please look ASAP". This drives our triage queue

Hit Submit request and the team gets pinged immediately.

What happens next

1. New — we've seen it, not started
2. In progress — actively being worked on
3. Waiting on you — we need a decision, asset, or answer before we can continue
4. Completed — shipped
5. Closed — wrapped (no further action expected)

You'll see status changes in real time on the request detail page and in your notification bell (if enabled).

Conversations

Each request has a conversation thread. Reply with anything — context, screenshots in the body, links to designs.

Replies appear like a chat:

• You on the right (muted bubble)
• Sites That Grow on the left (primary-tinted bubble)

Internal team notes are admin-only and never appear in your view.

Tips

• Attach images by description for now (we'll auto-pull from links you paste). File uploads are coming.
• One request per scope — easier to track, easier to estimate. Two unrelated things → two requests.
• Use sentiment honestly — it shapes how quickly we look. "Very worried" should mean something blocking; reserve it for that.