Software Development
Rather than adapting your business processes to off-the-shelf packages, we develop the software your processes actually require. The same team from analysis through to go-live and subsequent maintenance.
- AProcess mapping
- BScope document
- CInterface sign-off
- DWorking versions
- EGo-live
Mipo develops web and desktop software end-to-end for enterprise clients: technical analysis, interface design, development, testing, go-live and maintenance. Because the server and licence infrastructure the software runs on is also procured and installed by the same company, responsibility stays in one place.
Enterprise software in five steps, a deliverable at each.
At the end of each step you hold something concrete. There is no in-between state called “in progress”.
- A
Process mapping
The existing workflow is documented step by step; what needs software and what needs a process change are separated out.
↳ Process map and integration points list
- B
Scope document
What is included and what is excluded is written line by line and signed by both parties. The price is built on this document.
↳ Signed scope document and fixed price
- C
Interface sign-off
Screen flows are presented before development begins. Changes made at this stage are the least expensive changes.
↳ Approved screen flows
- D
Working versions
Versions are released to the test environment on two-week cycles. Each version genuinely works — it is not a demo.
↳ Working version in test environment + release notes
- E
Go-live
Data migration, parallel running period and user training. The old system remains open until the new one is verified.
↳ Go-live report and training record
Where an enterprise software project stands each week.
Two-week cycles keep the project visible. Months of “in development” followed by a surprise delivery don’t happen here.
Analysis and process mapping
Interface design and sign-off
Two-week development cycles
Data migration, training, go-live
What we build enterprise software with.
Typical project 8–16 weeks
What enterprise software development does not cover.
Items not in the quote are surprises that appear mid-project. With us, exclusions are also in writing.
- New screens and reports not in the scope document — priced separately
- Third-party software licence costs
- Process change training for the organisation's own staff
- Unlimited revisions — major changes after interface sign-off are a separate item
Questions about software development.
Yes. At the end of the analysis phase, the scope is fixed in writing and the price is confirmed against that scope. Out-of-scope requests are priced separately; there are no surprise cost overruns.
Yes. Unless otherwise stated in the contract, the source code, installation guide and database schema of the developed software are handed over to the client at project end.
Integration points are identified during the analysis phase. Systems with an open API are connected directly; those without one use a database- or file-based bridge for two-way integration.
If you wish, yes. Server hardware, operating system licence and backup infrastructure can be procured and installed by the same company, eliminating any responsibility gap between software and infrastructure.
The team that developed the project stays on for support. Bug resolution and planned development are carried out under the SLA-backed maintenance agreement; requests are tracked in a single file.