00Services
Custom operational software replaces the workbooks and email threads your process runs on.
Operational software is the system your team runs the work in — intake, calculations, approvals, evidence, and reporting in one place instead of five. Aptixx designs and builds it for field calculation and reporting, capacity planning, case management, and multi-site operations.
01The service map
Six services run on the same buying path.
Every engagement starts the same way: a free 20-minute fit call, then a fixed-fee discovery sprint. Pick the page that matches your problem.
Operational software
Workflow, calculation, field, and portal systems — this page.
Regulated operations
Roles, audit trails, and evidence for work a regulator reviews.
Customer & partner portals
Structured requests, secure documents, and live status for the people you serve.
Solution architecture
The system defined, priced, and specified before a build is committed.
MVP development
A startup’s first product, built to production standard on a fixed scope.
Process automation
The manual steps between your systems, found and absorbed by software.
02Definition
Operational software is the system the work runs in.
Not a website, not a dashboard bolted onto a spreadsheet. It is the place where a job is taken in, calculated, approved, evidenced, and reported — with the rules of your trade written into it.
Most businesses arrive here the same way. A process that worked at ten jobs a month is now running at a hundred, held together by workbooks, email threads, and the one person who understands the formulas. Custom operational software replaces that arrangement with one system built around your rules. Five characteristics separate it from generic business software:
- 01It follows your process rather than a vendor’s idea of it.
- 02It carries the domain rules — the tables, tolerances, and formulas your business is judged on.
- 03It produces the real outputs: certificates, plans, reports, records.
- 04It has roles, because different people are allowed to do different things.
- 05It keeps a record of who did what, so the output can be defended months later.
03Who it is for
Time, rework, and key-person risk surface the same five ways.
Five specific operating situations where a custom build is worth costing out, drawn from field calculation and reporting, capacity planning, case management, and multi-site operations.
- 01Field crews record readings on paper or a phone, and someone retypes them into the spreadsheet that produces the certificate.
- 02A capacity or demand plan lives in one workbook, and only its author can safely change the formulas.
- 03Cases move between intake, review, and follow-up across email threads, with no single record of where each one stands.
- 04Multiple sites report into head office in spreadsheets that arrive in different shapes every month.
- 05An off-the-shelf platform covers most of the process, and the rest runs on exports, macros, and one person’s memory.
Where readings taken on a vessel or a site have to become a defensible certificate, start with field and marine operations software. Where several sites and shifts have to report into one operational picture, start with manufacturing and production operations software.
04What Aptixx builds
Four kinds of systems share one standard of evidence.
Most operational builds are one of these four, or a pair of them working together. What each one changes in the operation matters more than its feature list.
Workflow & operations systems
Intake, approvals, stages, exceptions, ownership, and status coordinated in one system instead of five inboxes. The queue is the software, not a person’s head.
→ One place where work moves and everyone can see it
Calculation & planning products
Domain rules, interpolation tables, and forecasting models become repeatable, reviewable decisions — with the inputs and the version recorded alongside the answer.
→ Decisions you can re-run, review, and stand behind
Field, evidence & reporting tools
Capture the work once — readings, inspections, site records, photos — and generate the certificate, report, or submission from that same record automatically.
→ Capture once, report without re-typing
Customer & partner portals
Structured requests, secure documents, and live status that replace unstructured back-and-forth. See customer and partner portal development.
→ Fewer status calls, clearer shared process
05How delivery works
Scope and cost are fixed before the build starts.
Four steps, each one bounded: a free 20-minute fit call, a fixed-fee discovery sprint, the smallest operational MVP that changes the work, then improvement on evidence. Every step produces something you keep.
The paid discovery sprint is where scope, integrations, and cost stop being guesses. Read what a discovery sprint delivers, including the outputs, the exclusions, and how the fee credits toward a build. After handoff, an optional monthly retainer keeps Aptixx on call for support, monitoring, and the next workflow — month to month, and the software is yours either way.
The sprint fee is fixed before it starts and credits toward the build. The workflow map, the prototype, and the build definition are yours whether or not you continue.
06Engineering standards
Risk lives in the parts nobody demos.
Operational systems get audited, disputed, and inherited by the next person. Five practices decide whether that goes well.
- 01Typed code end to end. The shapes moving through a calculation are checked at build time, not discovered in production.
- 02Automated tests around the rules that matter. The marine survey platform carries 1,630 automated test cases across roughly 100 test files, concentrated on the calculation engine.
- 03Versioned database migrations. Every schema change is a numbered, reviewable file — 46 of them in the marine survey platform, 210 in Trazo OS, built under contract.
- 04Row-level security at the database, not just the UI. A live audit of Trazo OS confirmed row-level security enabled on 117 of 117 tables.
- 05Decimal-safe math where money and measurements meet. Survey arithmetic runs in 20-digit decimal, never floating point, because a rounding artifact on a signed certificate is a commercial dispute.
Those five standards are why the marine survey platform can stand behind a fleet-wide hydrostatic audit across all 17 barges, run read-only against production, and an engine that reproduces a previously issued, signed survey certificate to the cent.
Counts verified in August 2026 against the codebases and a live database audit.
Twenty minutes on your workflow, free, and a straight read on fit either way.
07Engagement model
Ownership, accountability, and scope are settled up front.
Three commitments decide whether an engagement is worth starting. If what you need is a themed site, rented developers, or an open roadmap, another firm will serve you better.
Built around your process
Your operation is never fitted to a theme and a page builder. A custom build earns its cost only where an off-the-shelf tool cannot carry your rules, and the discovery sprint is where that gets settled.
One firm accountable
You are not renting seats. Aptixx owns the architecture, the trade-offs, and whether the system holds up in the field.
Bounded at every step
A fixed-fee discovery sprint, then a scoped MVP. Each step stands on its own. The monthly retainer after handoff is explicit and month to month, against a named workflow rather than an open roadmap.
The adjacent problems each have their own page. Work that carries regulators, inspectors, or auditors: regulated operations software. What your customers and partners get to see: customer and partner portals. A problem without a defined system yet: solution architecture. A startup’s first product: MVP development. Cost sitting in manual work rather than a missing system: process automation.
Next step
Bring the workflow your business has outgrown.
Twenty minutes on your process: what a custom build would cover, what it would not, and whether it is worth costing out. You keep the read either way.