Process automation
Recurring work across email, documents, tickets and data, handled by software, and the systems a business already uses connected to each other.
Caelestis · software studio
We build software and automate business processes.
Current engineering and AI practice keeps the path from the first sketch to a system in production short. Go and Rust throughout.
What we do
Software
Services, tools and applications in Go and Rust, delivered through the same process.
How an engagement runs
0
Fit
A short written intake. Together we decide whether the work suits both sides.
You receive a decision, with reasons.
1
Scope fixed fee
The problem becomes a written scope.
You receive scope document, architecture outline, risks, milestone plan.
2
Decisions
Core decisions are written down and versioned: boundaries, data model, access, deployment. Changes after this point go through a change request.
You receive the decision record.
3
Build
Work arrives in milestones. Each one runs, has acceptance criteria and comes with a report of what was checked and how.
You receive, per milestone a working build, its acceptance criteria and the verification report.
4
Handover
A final review, and the documents needed to run the system without us.
You receive runbook, deployment guide, final review.
Rules we keep
- Written scope before code.
- Small deliveries, often.
- Every result is verified, and the verification is kept.
- Decisions are versioned.
- Asynchronous by default. Meetings have an agenda and an end.
- Payment per milestone, on acceptance.
A good fit for teams that want defined outcomes and written decisions. Staff augmentation and open-ended work without a defined result are outside the scope.