SIZ Digital.
Mobile apps, management software, web solutions and mobile money payments, designed in Abidjan for real field conditions: dropping networks, expensive data, modest devices, multi-operator payments. Hosting, maintenance and training included.
- Designed offline-first
- Costed specifications
- Code ownership in the contract
Four types of projects, one standard.
- Android and iOS, for entry-level devices
- Offline operation and synchronisation
- Field data collection and entry
- Notifications and messaging
- Business tools that replace spreadsheets and notebooks
- Migration of your existing data
- Roles, permissions and audit log
- Dashboards
- Client portals and secure areas
- Sites optimised for slow connections
- Business administration interfaces
- Complex business platforms
- Multi-operator mobile money collection
- Automated reconciliation and receipts
- Traceability and audit trails
- Without becoming a financial player yourself
Delivered software must also be hosted, protected and maintained.
We run GIMMO every day: we know what a server going down or an account left open costs. These services come with our projects, or with your existing software.
Deployment, automatic backups, monitoring and updates, on our servers or yours.
Accounts, roles and permissions, two-factor authentication, audit log, review before every release.
Incidents tracked through to resolution, fixes, Android and iOS compatibility.
Hands-on training for your users and administrators, backed by written materials.
We do not just deliver software: we run it.
Many providers deliver and then disappear. We built GIMMO, a property management platform that our own division depends on every day.
Dedicated areas for agencies, property managers, owners and tenants, each with their own permissions.
Rent demands, rent receipts, fees, reminders and owner statements.
Online reporting, assignment to contractors, tracking of quotes and works.
Profitability per unit or per building, history and centralised documents.
Tracking of due dates, rent reviews, document archiving.
Inventory reports and incident reporting on mobile, even on an unstable network.
Discover GIMMO and its modules · GIMMO at work at SIZ Immobilier · Request a demo
Designing for the field, not for the demo room.
An application conceived elsewhere often fails here, for reasons that have nothing to do with the code. These four constraints are built into the design from the outset.
Offline data entry and viewing, synchronisation when the network returns, conflict resolution rules defined with you.
Compression, caching, syncing only the differences: a data-hungry app ends up uninstalled.
Entry-level Android: app size and resource consumption are design criteria.
Wave, Orange Money, MTN MoMo, Moov Money: a flow that accepts only one of them excludes some of your customers.
Six steps. A deliverable at each one.
- 01Scoping
Workshops with your business teams, real user journeys, deciding what goes into the first version.
Deliverable Specifications and budget split into work packages - 02Design
Screen and journey mock-ups, tested with real users before any code.
Deliverable Validated clickable mock-ups - 03Iterative development
Short cycles, with an installable version at the end of each: you can change course early.
Deliverable A testable version at each iteration - 04Acceptance testing & data migration
Tests on real cases; spreadsheets, notebooks or legacy software migrated and checked.
Deliverable Acceptance certificate and migrated data - 05Go-live & training
Deployment, publication on the app stores if needed, onboarding of users and administrators.
Deliverable Documentation and training materials - 06Maintenance & updates
Fixes, Android and iOS compatibility, enhancements at the pace of your business.
Deliverable Maintenance contract and release log
We never hold the funds.
On any project involving payments, money flows directly between the parties via the mobile money operator or a licensed aggregator. We build the software that triggers and reconciles the payments.
Scope: SIZEG AFRICA publishes software. We are neither a bank nor a payment institution. A second product is being prepared by the same team; we will present it at launch.
What project owners ask.
How much does it cost to develop an application?
The cost depends on the number of user journeys, external integrations, the need for offline operation and the level of data requirements. We do not give a price range before scoping.
Scoping produces a costed scope, split into work packages, which you decide on package by package, including choosing to do only part of it.
Who owns the source code?
It is a contractual point, addressed from scoping onwards: scope of the transfer, technical documentation handed over, conditions for takeover by a third party.
Ask any provider this question before signing. A project where nobody knows who owns what becomes expensive the day you change partner.
Does the application work without a connection?
It is our default design principle: users enter and view data offline, and the data is uploaded when the network returns.
The real difficulty is resolving conflicts when two people modify the same data during the outage. These rules are decided with you, business by business.
Can you integrate mobile money payments?
Yes, through the operators' interfaces or those of a licensed aggregator, planning for several operators rather than just one.
Funds pass through these players, never through SIZEG AFRICA: we do not hold your users' money.
What happens after go-live?
Delivered software is not finished software: mobile systems evolve, partner interfaces change, your business moves on.
The maintenance contract sets out in writing the fixes, compatibility updates, response times and volume of enhancements included.
Where is the data hosted?
The choice is made with you, depending on the sensitivity of the data and your obligations. We document where the data resides, who accesses it, and how it is backed up and restored.
A backup that has never been tested is not a backup: restoration is part of acceptance testing.
Let's start by scoping the need.
Describe what your teams do today and where things get stuck. Scoping turns an intuition into a costed scope, and sometimes concludes that custom development is not the right answer.