SERVICES
Fix one workflow, properly.
Aethonex finds the workflow that costs you the most, scopes it in writing, and builds it end to end. You agree the price before work starts and you keep what is delivered.
THE PROBLEM
Four patterns that describe most of the work.
If one of these sounds like your business, there is a fixable workflow behind it.
A workflow nobody owns
Intake, reporting, or follow-up moves between tools and people by hand. Nobody can describe the whole path, so nobody can fix it.
A report rebuilt every month
Someone assembles the same numbers from several sources by hand, and the answer changes depending on who ran it.
Connectors that fail quietly
Integrations stop working without anyone noticing. The workaround becomes a spreadsheet and a reminder in someone's calendar.
A tool you cannot leave
The setup only makes sense to the person who built it, so changing it feels riskier than living with it.
WHAT WE DELIVER
Four kinds of work, all scoped in writing.
Workflow automation
Intake, routing, approvals, status tracking, follow-up, and handoffs between the tools you already pay for.
Reporting rebuilds
Recurring reports rebuilt from source so the numbers are produced rather than chased.
Systems integration
Connecting tools that do not talk to each other, with visible failure handling instead of silent breakage.
Owned handover
The practical side of ownership: access, code, runbook, and a recording of how to run it.
HOW ENGAGEMENTS ARE STRUCTURED
Start at the level of certainty you already have.
15–20 minutes · Directional
A directional 12-month cost for one workflow in tool spend and internal time.
SaaS Exit Blueprint · 5 business days
What you run, what it costs over 12 and 36 months, where it breaks, and which workflow to fix first.
One Workflow, Owned · Fixed build · 2 × $450 or 3 × $300
One workflow automated or rebuilt end to end, delivered with access, code, and documentation.
Stack Ownership Sprint · 10 business days · 3 × $1,500
Stack and cost mapping, fragility and dependency review, one workflow rebuilt and deployed in an environment you control, plus a written roadmap and ownership pack.
LARGER ENGAGEMENTS
Multi-system rebuilds are quoted privately.
Broader rebuild work - including client reporting rebuilds that span more than one team or data source - is scoped and priced only after a Sprint, using the budget range you provide. It is not published as a fixed public price, and it is not offered before the smaller stages have shown what is actually needed.
Discuss a larger rebuild →PROJECT FLOW
What happens, in order.
Six stages from first conversation to handover. Each one has a defined output.
Written scope
Deliverables, exclusions, timeline, price, and owner for each item. You approve it before anything is built.
Access and environment
We agree where the system will run and how it will be reached. Access is provisioned for the build and revoked or rotated at handover.
Build on real data
The workflow is built against your actual data and tools, not a sample environment.
Review
You walk through the running workflow, raise gaps, and we correct them inside the agreed scope.
Agreed handover
Access, source code, documentation, and a recorded walkthrough are transferred on a scheduled call.
After handover
The system is yours to run and change. Further work is a new, separately scoped engagement - never an implied retainer.
OWNERSHIP AND HANDOVER
Delivered with agreed handover and ownership rights.
Where the engagement includes a delivered system, the customer receives the ownership rights, deliverables and documentation agreed in the engagement terms. Built for your team to operate and keep. Delivered systems run in an environment you control — your own server, your own hosting account, or another customer-controlled infrastructure you nominate.
- Administrative access to the environment the system runs in, in your name.
- Agreed deliverables, source code, and configuration for custom systems built for you.
- A written runbook covering how the workflow operates, handles failure, and is maintained.
- A recorded walkthrough on the handover call for operational clarity.
- Explicit confirmation of deliverables and ownership terms confirmed before the build starts.
- No forced dependency on Aethonex to keep it running, and no implied recurring software seat fees.
Aethonex retains pre-existing IP, reusable frameworks, generic components, and internal tooling unless explicitly transferred by contract. Where a system processes customer data, it operates strictly within your security perimeter under the agreed written scope.
SERVICE QUESTIONS
Before you commission anything
Start a Project.
Start with the free Exit Number, or tell us directly which workflow is costing you the most.
[email protected] · +44 7348 954852