Discuss your project
Software & Cloud Development

Custom software development

Some processes are too specific, regulated or important for a generic product. We build applications around how you work, connect them to your systems, and hand over code and documentation you own.

Discuss your project How the work is delivered

A good fit if

  • A core process runs on spreadsheets, email or an old database few understand.
  • Packaged products you evaluated all need expensive workarounds.
  • An ageing in-house application needs replacing or modernising without losing data or business rules.
  • Your distinctive process must share data with your ERP, CRM or Microsoft 365, not become a silo.

What is included

  • Build, buy or integrate assessment, with the reasoning written down
  • Requirements, business rules, exceptions, roles, data model and architecture
  • The application, built iteratively with regular demonstrations
  • Migration from spreadsheets or legacy systems, with reconciliation reports
  • Role-based access, audit logs, single sign-on, tests, repeatable deployments
  • Documentation, training, handover; code and infrastructure in your accounts

What this service is

An application built for how your organisation works, instead of bending your work to a packaged product. It fits less often than custom-software vendors suggest, and very well when a process matters and generic tools handle it badly.

  • Field inspection and work orders
  • CRM for specialised sales or intake
  • Transportation and dispatch
  • Quoting and pricing engines
  • Case and file management
  • Compliance registers
  • Client portals tied to internal records
Features we plan from the start

Sign-in through Microsoft Entra ID or Google, role permissions, approval workflows, email and Microsoft Teams notifications, document and PDF generation, search, reporting dashboards, data exports for finance and an audit trail. For users away from a desk, a mobile app or offline mode, which also helps where connectivity is patchy; where users need more than one language, screens and generated documents that support it.

Build, buy or integrate

Buy

Configure a mature product, for common processes it fits closely.

Integrate

Move data between your tools without retyping; often quickest. See integration.

Build

A custom application or ERP module, when fit is poor, workarounds are costly or the process is an advantage.

More in build, buy or integrate? AI features, such as plain-language search or drafting help, get the same testing and access control: see generative AI development.

Modernise and maintain

Replacing an old Access database or spreadsheet system is a common start. Legacy tools (Access databases, outdated desktop applications, web systems on unsupported frameworks) often hold unwritten rules. We document what they do and who relies on them, then rehost, refactor gradually, or replace piece by piece with old and new running together: slower on paper, far less risky than one cut-over.

On Prometheus or ERPNext we often build inside the ERP, sharing its users, permissions and data (customisation), unless users, scale or security model differ greatly. Managed-service clients can add 24/7 monitoring and support, with response targets in the service agreement.

Built to be maintained

Widely supported frameworks, code in your repositories, automated tests, documented architecture and business rules, and repeatable deployments. The result: staff spend time on the business instead of workarounds, costs are planned in phases with estimates in naira (or US dollars where a licence or service is priced in dollars), data is protected by role-based access and audit trails, and the application grows with you.

Delivery

How the work is delivered

  1. Assess

    Map the process, people and systems it touches; compare building, buying and integrating.

    Output: Assessment and recommendation.

  2. Specify

    Capture rules, roles, data and exceptions, and agree what the first release must do.

    Output: Requirements and release plan.

  3. Build iteratively

    Short iterations with working demonstrations; priorities can change between them.

    Output: Tested increments in a test environment.

  4. Migrate and go live

    Move data, run old and new side by side where needed, reconcile, then switch over.

    Output: Live application and reconciliation evidence.

  5. Hand over

    Documentation, training, credentials and code transfer, with an optional support agreement.

    Output: Handover pack.

Scope at a glance

Not included unless agreed

  • Licences, hosting and third-party services, billed with your approval
  • Cleaning historical data beyond the agreed migration scope
  • Process redesign or support after handover, unless separately agreed

What we need from you

  • A process owner who knows the rules and edge cases
  • Workshop and test users; access to existing tools and data
  • A hosting decision: your cloud, your servers or Promatics-managed

Before handover

  • Rules and role access (what each must not see) tested with real cases
  • Migrated data reconciled: record counts and totals signed off
  • Rebuildable and redeployable from the repository by anyone, not just Promatics

What affects the cost

  • Business rules, exceptions, roles and approval paths
  • Integrations with other systems
  • Volume and condition of data to migrate
  • Audit, data protection and records-retention requirements

No package prices: estimates in naira from an agreed scope, taxes shown separately.

Questions buyers usually ask

How do you decide between building and buying?

We weigh product fit, workarounds, cost over several years and how much the process matters. If a product fits, we recommend it; custom software earns its place when the fit is poor or the process is a genuine advantage.

Who owns the software?

You do. The agreement assigns ownership of the code written for you, kept in repositories and cloud accounts in your organisation's name. We list the open-source components and their licences.

What if our requirements change during the project?

They usually do. You can reprioritise between iterations, and changes that affect scope or estimates are agreed in writing before work continues.

Guide

Build, buy or integrate?

How to choose between buying, integrating and building software, with a fair weighted worksheet.

Service

Business system integration

Connect your applications so data is entered once, moves reliably, and failures are caught, not lost.

Outgrown your spreadsheets or legacy system?

Describe the process, the tools it runs on today and who uses it. We will reply to arrange a conversation about building, buying or integrating.

Discuss custom software