§ Experia.dev
Software development, priced by the story point.
Experia.dev is the build arm of Experia Systems. We write software to commission, keep production systems supported and maintained, and ship new features onto the platforms you already run. Sized in story points, billed on what ships.
§ 01 · Workstreams
Three ways to put engineers on the problem.
The same team, the same standards, whether the system is ours from the first commit or inherited in production.
On commission
Bespoke systems built to order: scoped from your requirements, delivered in controlled increments, and handed over working, with the documentation and the deployment pipeline as well as the code.
Support & maintenance
Ongoing care for systems in production, ours or inherited. Fixes, patches, upgrades, and monitoring under an agreement that states response expectations in writing.
Platform & feature development
New modules, integrations, and features on platforms you already run, extending the system you have without destabilising it, one sized release at a time.
§ 02 · Commercial model
How we charge.
Development work is broken into stories, sized before work starts, and billed at an agreed rate per story point. The size is fixed when you approve it. If a story takes us longer than sized, that's our problem, not your invoice.
| Line | How it works | Covers |
|---|---|---|
| Story points | Scope is decomposed into sized stories and billed per point at rates by role and seniority. You approve the sizing before delivery begins. | Commissioned builds, feature development, and sized maintenance work. |
| Project management | The one hourly line: PMO effort billed per hour against the delivery it coordinates. | Planning, coordination, reporting, and release management. |
§ 03 · Delivery
The same loop, closer to the code.
Every workstream runs the firm's delivery loop: through to production, and then around again.
Understand
Clarify the business problem (the users, systems, processes and constraints around it) before anyone proposes a tool.
Architect
Design a practical solution covering technology, integration, operations and governance. Practical means buildable, and runnable by the team you actually have.
Build
Implement in controlled, incremental phases: working software early, disruption managed, assumptions tested against reality.
Operate
Support, monitor and govern the production environment. We stay accountable for the system in production, not just at handover.
Improve
Use operational data and business feedback to keep improving the system: deliberately, on a cadence, not only when something breaks.