Service lanes we runProduct
Suggested engagements for this lane. Contact opens with this service selected; a confirmation is emailed to the address you enter.
Custom software
Custom software at Aarvix Services is a written scope, then a build. Discovery produces the boundaries, the risks, and a plan you can accept or stop. A business application is an internal tool your staff use every week. A SaaS MVP is the first release of a product you intend to sell.
We do not start a build from a slide. The hour block for discovery is separate from the hour block for the build, so you can pause between them.
How an engagement runs
-
01
Discover
Map the workflow, the users, and what is out of scope for this release.
-
02
Plan
A written scope, a sequence, and the hour block for the build.
-
03
Build
Implement the agreed release and review it against the scope.
-
04
Release
Handover, access, and a note on what the next block would cover.
What you leave with
- A scope you can accept before build hours are spent
- Software your team uses in the real workflow, not a demo
- A release you can put in front of staff or early customers
Hour packs tied to this lane
Discovery
A software idea that is real, but not yet bounded.
Business application
Operations, finance, or delivery teams replacing a manual process.
SaaS MVP
Founders who need a first release, not a full platform.
Included in the build
Custom software
Discovery is a block you can stop after.
Custom software at Aarvix Services is a written scope, then a build. Discovery produces the boundaries, the risks, and a plan you can accept or decline. A business application is an internal tool for a workflow your staff already run in inboxes and sheets. A SaaS MVP is the first release of a product you intend to sell: accounts, the core job, and a way to see whether anyone uses it.
We do not start a build from a slide. The discovery hours are separate from the build hours so you can pause between them. That pause is the point. A lot of software engagements should end at the plan, when the plan shows the job is smaller than a product or larger than this quarter.
If what you need is a connection between two tools you already pay for, that is an integration, not a new application. If what you need is a public site, that is a website. Software is for a tool your team or your customers will open on purpose.
Sequence
What discovery is expected to leave behind
- 01
The users
Who opens the tool, how often, and what they do in the first minute.
- 02
The boundary
The release that is in, and the list that is explicitly out.
- 03
The risks
Data you do not have, a system we should not replace, a workflow that is still changing every week.
- 04
The plan
A sequence and the hour block for the build, which you can accept or stop.
Software questions
Is a SaaS MVP a full platform?
No. It is the first sellable release: the core job, accounts, and enough visibility to see if the job is used. A platform is a later block, if the first release earned it.
Can discovery and the build be one purchase?
They are two lines so the second can be declined. We can write them in one scope if you already know you want both, and the scope will still show them as separate blocks of hours.
Do you replace our database?
Only if the scope says the new tool owns that record. Otherwise we read from the system that already does.
Need a different shape of work?