Suggested engagements for this lane. Contact opens with this service selected; a confirmation is emailed to the address you enter.
Support
Support is for the week something small is wrong: a form, a login, a page, a workflow that stopped. It is not an unlimited help desk. You buy a monthly block. Unused hours do not roll. The person who answers already knows the work because they are on the same studio account.
Urgent items are named in the request. Everything else waits for the block. If a fix is larger than the month, we say so before the hours are spent.
How an engagement runs
-
01
Open
Send the symptom, the page or system, and who is blocked.
-
02
Sort
We mark it as a fix inside the block, or as a separate engagement.
-
03
Fix
Hours from the monthly block are spent on the agreed items.
-
04
Close
You get a short note of what changed and what is left.
What you leave with
- One place to send a break, instead of a group chat
- A monthly ceiling you can see before the month starts
- A note when a request is really a new project
Hour packs tied to this lane
Support starter
A calm month with occasional breaks.
Support plus
Teams with a weekly trickle of small requests.
Launch watch
The fortnight after a site, workflow, or integration ships.
Included in the build
Support
A named contact for the small break, and a rule for the large one.
Support is for the week something small is wrong: a form, a login, a page, a workflow that stopped. It is not an unlimited help desk and it is not a place to hide a new project. You take a monthly block. Support starter and support plus are the hour times 30. Launch watch is a short, heavier project block for the fortnight after something goes live, priced per hour.
Unused hours do not roll. Urgent items are named in the request. Everything else waits for the block. If a fix is larger than the month, we say so before the hours are spent and point you at a fixed engagement. The person who answers should already know the work, because support is for systems the studio has touched or has been shown properly.
After a workflow or a site ships, the breaks often fall into a group chat. The support block is the replacement for that chat: one place to send the symptom, a triage against the month, and a short note of what changed.
Send a support note with these four lines
- 01The symptom
What a person saw, not a theory about the cause.
- 02The surface
The page, the inbox, the tool, the hour it broke.
- 03Who is blocked
A named role, so we can tell a fix from a preference.
- 04Whether it is urgent
Urgent is named. Unnamed work waits for the block.
Need a different shape of work?