A services studio with the price on the first page.
Aarvix Services takes on the work operating companies usually split across a web shop, a software vendor, and an automation freelancer: public sites, internal tools, a first product release, AI with a review step, and the handoffs between inbox, sheet, and system.
Project work is priced per hour. Monthly care and capacity are that hourly rate times 30. A written scope confirms the figure before any work starts.
Bundle sizes follow the shape of published starting prices for this kind of work — landing pages, business sites, discovery, MVPs, AI pilots, agents, workflow automation, and monthly care — restated on that single rate. A bundle is a starting point. The next step is the contact form.
How we price and decide
Three pledges before a scope is written
-
01
Hourly, or a month
Project work is an hourly rate. A monthly engagement is that same rate multiplied by 30.
-
02
Scope before build
Fixed work has a written boundary. Open work is a prepaid block. Monthly work is a fresh allocation that does not roll over.
-
03
A person still decides
AI and automation name the review step. If something can leave the building, someone on your side approves it.
The practice
One studio for the work that usually gets split.
-
01
Companies come to Aarvix Services when the public site, the internal tool, and the messy handoff between them are being bought from three vendors who have never seen each other’s scope. We would rather name the blocks separately and do them in one place, so the site and the workflow can share a boundary.
-
02
The price is on the first page because a hidden rate wastes the first conversation. Project work is an hourly starting rate. Monthly work is that rate times 30. A bundle size follows the shape of the job: a landing page is not priced like a SaaS MVP, and a support month is not priced like an agent build.
-
03
We will say no. A workflow that happens twice a year does not need a connection. An AI draft that cannot cite a source does not get sent. A site with no offer does not get a visual design first. Refusal is part of the service, not a mood.
What we keep
Habits you should be able to see in the work.
-
Scope
Write the edge first
Fixed work has a boundary. If the boundary is not ready, the engagement is discovery. We do not start product code from a slide.
-
Review
Name the person
Every automation has an exception path. Every AI job names who sends the draft. The hour covers the loop, not unlimited model spend.
-
Handover
Leave a runbook
You should be able to explain the page, the connection, or the prompt when a column name changes. Care is optional and separate.