Skip to content
Aetenum
Book a call

How it works

You send the thing. I scope it, write it down, build it, and hand it over.

Every item of work moves through the same five steps, and only one item is ever in the seat at a time. That constraint is the product. It is why things finish.

The sequence

Five steps, every time, no exceptions

  1. 01

    Ask

    You send the thing you want. A sentence is enough. There is no form to fill in and no discovery invoice attached to it.

  2. 02

    Scope

    I work out what it actually takes, and whether the thing you asked for is the thing you need. Sometimes the answer is a smaller build. Sometimes it is a different one.

  3. 03

    Draft

    You get the scope in writing. What gets built, what it touches, what it will not do, and roughly how long it holds the seat.

  4. 04

    Sign

    You approve the draft or you change it. Nothing gets built off a conversation, so we do not argue later about what was agreed.

  5. 05

    Build

    I build it, deploy it, document it, and hand it over. Then the seat moves to the next item on your list.

What the first week actually looks like

You send me a list. It does not need to be organized or technically accurate. A list of things that are broken or missing is enough, in whatever order they occur to you.

I read it and come back with two things: which item I think should go first, and why. Sometimes that is the item at the top of your list. Often it is not, because something further down is the reason the top item keeps breaking.

Then I scope that first item and send it to you in writing. You approve it or you change it. Once it is approved I start building. In most first weeks something is deployed before the week is out. A heavy data migration is the usual exception, because the first days of one of those are spent reading the source system rather than writing anything.

How pausing works

This is the part people actually worry about, so here it is plainly. The fear is not the price. It is signing something open-ended.

You can pause or cancel at any time, effective at the end of the month you have already paid for. Pausing does not produce a refund. It banks the unused days, and those days roll forward to whenever you resume. They do not expire.

You can pause between items freely. If an item is mid-build when you want to pause, that item either finishes or we agree to stop it and take it off the list. What does not happen is a half-deployed system left in your stack with nobody responsible for it.

There is no long-term contract, no notice period, and no minimum term.

What a seat includes

Included

  • Scoping and discovery for every item, before any code is written
  • Architecture and build
  • Deployment, documentation, and handover
  • Judgment. I tell you when the thing you asked for is not the thing you need

Not included

  • A second simultaneous build stream. That is a second seat
  • Emergency or after-hours response, unless we agree it separately
  • Licenses, hosting, and third-party fees
  • Managing your staff or your other vendors

What people point the seat at

You decide the order. These are the categories the work usually falls into.

Questions people actually ask

What does week one look like?
Day one you send me your list. I scope the top item and send it back in writing, usually within two working days. Once you approve it, I start building. Most first weeks end with something deployed, though a heavy migration is an exception to that.
What happens if I pause?
Billing stops at the end of the month you have already paid for. Unused days are not refunded. They are banked and roll forward, so when you resume you start with those days available. Banked days do not expire.
Can I pause in the middle of a build?
You can pause between items at any time. If something is mid-build, that item finishes first or we agree to stop it and take it off the list. Nothing gets abandoned half-deployed.
What if I do not know what I need built?
That is normal, and it is the part I am actually there for. Describe the problem rather than the solution. Working out whether the thing you asked for is the thing you need is included in the seat, not billed as a separate discovery phase.
How big can one item be?
Large projects get decomposed on my side rather than yours. A migration that would take two months becomes a sequence of items that each land and go live on their own, so you see progress continuously instead of waiting until the end.
What if I need two things at once?
That is a second seat. One seat is one active build stream, and the reason it works is that it is never split. A second seat starts at $6,500 per month.
Who owns what you build?
You do. Code, infrastructure, documentation, and accounts are yours, and they are handed over as part of the build rather than held as leverage.
What happens if I cancel?
Cancel any time, effective at the end of the current paid month. Everything built up to that point is already deployed, documented and in your hands. There is no exit project and no final invoice for handover.

Start with a call, not a contract

Thirty minutes. You describe what broke, what it is costing you, and what you have already tried. I tell you whether a seat is the right answer, and I will tell you when it is not.

Book a 30 minute call See what it costs

Or reach me directly: +1 385-208-1781 scott@aetenum.com

If you are comparing quotes on price, I am not your cheapest option and I will not pretend otherwise.