Service lanes we run
Open the hourly rate sheetService lanes we run
The lanes this desk runs.
Each lane names the work, the run, and the hour bundles that usually fit. A project stays on the hourly rate. A month is that rate times 30.
Sites
Websites
Landing pages and company sites for businesses that need a clear public presence, not a theme with a logo dropped on it.
More about this lane →Product
Custom software
Internal tools and a first product release, with discovery priced before product code starts.
More about this lane →AI
AI software
Pilots, application sprints, and agent workflows with a person still responsible for what gets sent.
More about this lane →Workflows
Automation
The repetitive handoff between inbox, sheet, and system, built once and left running.
More about this lane →Hours
Capacity
Prepaid hours and monthly blocks for work that is real, but does not fit a single fixed scope.
More about this lane →Search
Search and content
On-page search, a content model, and a monthly writing block for pages that should be found.
More about this lane →Systems
Integrations
Connect the tools you already pay for, with a map of what talks to what and who owns the failure.
More about this lane →Care
Support
A named contact and a monthly hour block for the small breaks that should not become a project.
More about this lane →How to use this page
Every service is the same shape of page, on purpose.
An Aarvix 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
- 01The job
One offer, one workflow, or one queue. Not a department.
- 02The record
Which system is the source of truth, and which fields are allowed to move.
- 03The person
Who approves a draft, a page, or an exception before it leaves the building.
- 04The edge
What this block will not do, written down before the hours start.
- 05The handover
What you can run without us, and what care would cover if you want it.
- 06The next block
Optional. Named only if there is an obvious second step, never as a silent continuation.







