IT Solutions & Software Development
Software development at Obsidra means designing and building web, mobile and platform software from a written specification grounded in research about who will use it.
Scope
What this is
Product engineering from specification to production. We write the specification with you, agree the architecture, build in short increments you can review, and deploy to infrastructure you control. When we inherit an existing system, we read it before we change it.
Software built from a written specification can be checked against that specification, one journey at a time.
What is included
- Web applications and mobile apps for iOS and Android
- Custom platforms: portals, internal tools, booking and operations systems
- APIs and integrations with the systems you already run
- Cloud setup, CI/CD pipelines and monitoring
- Support, maintenance and planned improvements after launch
Architecture
A typical system shape
Most builds share this outline. The architecture notes record where yours differs and why.
Inputs
What we need from you
A build starts once these four are in place.
- A product owner who can accept or reject each increment
- The user journeys you already know of, even as rough notes
- Access to the systems the product must connect to
- Cloud accounts in your name, or approval to open them for you
Deliverables
What you get
Every build ends with the same set of artefacts, so another team could pick it up.
| Artefact | Form | Volume | For whom |
|---|---|---|---|
| Running software | Deployed to your cloud account | A first production release, then planned increments | Your users |
| Source code and infrastructure scripts | Your repository | Everything needed to rebuild the system from nothing | Your engineers, or a future vendor |
| Architecture notes | Written document | The main decisions and their trade-offs | Technical leads |
| Runbook and admin guide | Written documents | Deploying, restoring, monitoring and daily administration | Operations and support staff |
Indicative timeframe: six to sixteen weeks for a first production release, depending on scope and the number of integrations.
Process
How we run it
Specify
User journeys, data model and integrations written down and agreed. Anything unclear becomes a question, not a guess.
Design the architecture
We choose a stack your team can hire for and run. The choice and its trade-offs are recorded.
Build in increments
Short cycles, each ending in a working demo on a staging environment you can open yourself.
Harden and launch
Testing, security review, performance checks and a launch plan with a rollback path.
Support
Monitoring, fixes and planned improvements under the support model agreed before launch.
Glossary
Terms on this page
- Specification
- The written description of user journeys, data and integrations that the build is measured against.
- Increment
- A small, working and deployable part of the product, delivered and reviewed in one cycle.
- Staging environment
- A copy of production where each increment is reviewed before it is released.
- Runbook
- The operating instructions of a running system: how to deploy it, restore it and respond to alerts.
Questions
Questions about software development
Fit
When this is not for you
- An off-the-shelf product already does what you need. We will tell you, and configuring it will cost far less than building.
- You need a quick prototype to test an idea with a few users. A no-code tool is usually the better first step.
- Nobody on your side can make product decisions during the build. Custom software stalls without an owner.
Next step
A system to build or take over?
Tell us the decision or the system in front of you. On the intro call we say which service fits, what we would need to start, and whether we are the right team.
Book an intro call