A1 Services desk

Services

The services the studio takes on.

Each service page is the same template: what the work is, how it runs, and the hour bundles that usually fit. Project work is an hourly rate. Monthly work is that rate times 30.

How to use this page

Every service is the same shape of page, on purpose.

An A1 Services service page tells you what the work is, how an engagement runs, what you leave with, and the hourly lines that usually fit. Project lines are a rate per hour. Monthly lines show that rate times 30, with the hourly figure underneath so the month is not a mystery.

The lines are starting points, not a menu you add to a cart. Open one and the contact form already knows the service. If you are between two services, write that in the message. A website with a small order workflow is often a site first and an automation second, as two blocks, so you can stop after the first.

Capacity and support are not substitutes for a missing scope. If the queue is real but the job has no edge, say so. If the job is a new product surface, it belongs under custom software or an AI pilot, not under a monthly block that was meant for edits.

What every engagement is expected to name

  • The jobOne offer, one workflow, or one queue. Not a department.
  • The recordWhich system is the source of truth, and which fields are allowed to move.
  • The personWho approves a draft, a page, or an exception before it leaves the building.
  • The edgeWhat this block will not do, written down before the hours start.
  • The handoverWhat you can run without us, and what care would cover if you want it.
  • The next blockOptional. Named only if there is an obvious second step, never as a silent continuation.