How we work
No surprises and no unexpected invoices. You approve the plan before the first line of code is written.
Discover
We start with a conversation, not a proposal. The point is to understand what problem the system solves, who will use it, and under what real conditions it has to run: available bandwidth, power cuts, the devices your staff actually carry, and the paper processes that hold the operation together today.
- Interviews with the people doing the work, not only with management
- Inventory of existing systems, spreadsheets and paper forms
- Real constraints: connectivity, power, budget and calendar
- Measurable success criteria agreed in writing
Design
With the problem clear, the solution gets defined: architecture, data model, user flows and scope. All of it is written into a document you review and approve. This is the cheapest possible moment to change your mind, and the process deliberately makes room for it.
- Technical architecture and a justified technology choice
- Interface design and user flows reviewable before any coding
- Closed scope, with what is excluded stated explicitly
- Phased delivery plan with milestones and responsibilities
Build
Development runs in short cycles with regular demonstrations of the real system. Every increment carries version control, testing and a security review. You do not wait months to see something: it is running within the first weeks.
- Regular demonstrations of the real system, not mockups
- Version control and separate staging and production environments
- Security review and data validation in every module
- Technical documentation written as the work happens, not afterwards
Deploy
Going live is planned: data migration verified record by record, backups before every change, a rollback plan and staff training. A deployment is not finished until the team uses the system confidently.
- Data migration with verification and a rollback plan
- Domain, certificate, email and backup configuration
- Training on site or remotely, in Spanish, French or English
- User manuals and administration documentation delivered
Support
After launch the system is still alive. A clear support agreement covers monitoring, backups, security updates and the improvements that real use inevitably reveals.
- Uptime monitoring and verified backups
- Security and dependency updates
- Response times agreed in writing
- Improvements and new features prioritised with you
Three engagement models
Project
A defined deliverable built to an agreed scope and timeline.
Fixed scope · fixed price
Retainer
Ongoing development, maintenance and support each month, with flexible hours.
Monthly · flexible hours
Advisory
Strategy, systems audits and technical guidance on demand.
Per engagement
Frequently asked questions
How much does a project cost?
Price depends on scope, and scope is closed during the design phase. After a first conversation you receive a written proposal with scope, phases, timeline and price. That proposal carries no cost and no commitment.
Do you charge up front?
Projects are invoiced against milestones tied to verifiable deliveries, not against elapsed time. The specific split is agreed before signing.
What happens if scope changes mid-project?
The change is estimated in writing, with its impact on timeline and price, and you decide whether it goes in now, in a later phase, or not at all. No change is ever executed without prior approval.
Do you work remotely or on site?
Both. Discovery, deployment and training usually benefit from physical presence in Malabo or Bata; development happens remotely with no loss of quality.
Let us build something for Equatorial Guinea
Tell us what you want to achieve and we will come back with a clear plan, timeline and price. Available for on-site and remote engagements.