Software should outlast the team that wrote it
We document, we test, and we hand over. If your platform depends on a particular person staying, we have failed.
01Registered in Nigeria · RC 9385639
Engineering
transformative
digital solutions
We design, develop and deploy software platforms and technology infrastructure for businesses, institutions and government, and we build seven products of our own on the same foundations.
- 2026
- Incorporated
- 7
- Products in the group
- 150+
- Engineered modules
- 30+
- Live integrations
3 March, Abuja
across seven sectors
in production and in build
operated across the portfolio
Our mandate
To engineer transformative solutions, from digital platforms to next generation products, that improve lives, empower businesses and redefine technology.
01The company
One company, two arms that feed each other
What we learn building products we sell as services. What we learn on client work goes back into the products. The shared platform underneath means the sixth product cost a fraction of the first.
Services practice
client engagements
- Engineering
- Consultancy
- Design
- Production
- Training
- Audit
Product group
our own platforms
- ErasCare
- ErasTrade
- ErasPay
- SkulHive
- Quint
- KMS
- MUUV
Shared platform
Identity, access, audit, payments, notification, storage and reporting are built once and used by everything. A client engagement starts from working components rather than an empty repository.
What we believe
Structure before speed
A data model, a permission model and an audit trail decided at the start cost days. Retrofitted afterwards they cost quarters, and sometimes they cannot be retrofitted at all.
02Configuration over customisation
Business rules that vary should be settings, not forks of the source. It is the difference between a system that grows with you and one you replace in three years.
03Say the difficult thing early
If a plan will not work, the useful moment to say so is before it is built. We would rather have an awkward conversation in week one than a rescue project in month nine.
04Our story so far
- March 2026
Incorporation
ErasStack Ltd registered with the Corporate Affairs Commission as a private company limited by shares.
- 2026
Product foundations
Architecture, data models and access control designed across all seven platforms, on one shared doctrine.
- 2026
Engineering at depth
More than 150 backend modules and 30 external integrations built across the portfolio.
- 2026
Corporate presence
Company website, verification records and business infrastructure established for enterprise and government engagement.
- 2027
First deployments
NextPriority platforms reach production and the first paying customers, with the services practice funding the build.
02What we do
The practice, in full
Our mandate spans software development, digital transformation, next generation product engineering, and the commercialisation of proprietary technology. Most clients need three or four of these; a few need all of them.
The core of the practice. We build backend systems, application programming interfaces, web applications and mobile applications, and we operate them afterwards if that is what the client needs.
- An explicit data model where every record carries its owner
- Role based access control, configured per organisation rather than hardcoded
- An audit trail that records who did what, when, and under what authority
- Background job processing with retries and dead letter handling
- Notification across in application, email, SMS and push
- Reporting that reads from the same data the application writes
- Documentation good enough for a different team to take over
Design is not decoration applied at the end. It is the part of the process where the product is decided.
- Discovery and research into who the user is and where the current process fails them
- Information architecture: what lives where, and what a person can reach from where they stand
- Screen by screen design of every state, including empty, loading and error
- Design systems, so the tenth screen costs a tenth of the first
Hosting chosen for the regulatory position the client is in, with releasing made routine rather than an event.
- Cloud or regional data centre, chosen for the client's regulatory position
- Automated deployment pipelines, so releasing is routine rather than an event
- Separated development, staging and production with real data controls
- Structured logging, metrics, alerting and on call runbooks
- Scaling designed for the load the client will have, not the load they have today
- Backup, restore rehearsal and a recovery plan that has been tested
Most organisations have the data and cannot use it, because it sits in separate systems in incompatible shapes.
- Consolidation into one place with a consistent shape and a single definition per measure
- Scheduled, monitored pipelines, with failures that are visible rather than silent
- Dashboards for the people who run the business, exports for the people who audit it
- Decision support that answers questions rather than displaying numbers
We build AI into products where it earns its place, and we are explicit about where it does not.
- Assistants grounded in real records rather than generating plausible text
- Document processing with every extracted field traceable to its source
- Semantic search and matching with explanations rather than opaque scores
- Where a system acts on a person's behalf, the boundaries are enforced in code, not requested in a prompt
Delivered as prioritised findings an executive can act on, not a tool dump. Each finding comes with severity, the concrete failure it enables, and the fix.
- Code audit: correctness, injection surfaces, secret handling, dependency risk
- Architecture audit: trust boundaries, authentication, authorisation, data flow
- Data protection audit: what personal data is held, where, for how long, under what basis
- Infrastructure audit: exposure, hardening, patching, backup and recovery
- Process audit: access management, change control, incident response readiness
What gets tested, at which level, and what is deliberately not tested, decided rather than assumed.
- Test strategy naming what is deliberately not tested
- Unit, integration and end to end suites wired into the pipeline
- A repeatable release check before anything reaches production
- Performance testing against the load the system will actually see
- Structured user acceptance sessions with the people who use it daily
For organisations that know something has to change and want a defensible plan before they commit budget.
- Technology strategy: what to build, what to buy, what to retire, and in what order
- Architecture review: an independent read on a system, its risks and its realistic future
- Vendor selection evaluated against actual requirements rather than a feature matrix
- Technical due diligence: an honest assessment of what the code and the team really are
Removing the manual steps between systems that already exist, and migrating off systems that no longer fit.
- Process automation between systems that already exist
- Systems replacement without losing history or stopping operations
- Migration planning with a reversible path at every step
Public sector systems have a different centre of gravity. The record, the access control and the audit trail are the product; the interface is how people reach them.
- Registries where provenance and correction history matter as much as the current value
- Identity and access management across departments with different authority
- Workflow and approval systems that mirror an actual mandate
- Oversight reporting built so numbers trace back to source records
- Data residency and retention handled as a requirement, not a preference
Technology that looks unfinished is assumed to be unfinished. The creative practice exists so the public face matches the platform underneath.
- Brand identity: naming, mark, palette, typography and the rules that keep them consistent
- Digital presence built to load fast and pass business verification
- Reports, profiles, decks and proposals produced to a standard that survives being forwarded
- Motion and video: product demonstrations, explainers, launch material
- Photography and art direction for teams that keep reaching for stock
Most organisations do not have a content problem, they have a system problem: nobody owns the calendar, nothing is reusable, and the channel goes quiet for a month.
- Content strategy: what this organisation should be known for, and what only it can publish
- Editorial production on a calendar rather than on impulse
- Day to day channel operation, scheduling and a consistent voice
- Community management, including the difficult conversations
- Reporting in plain language, and what changes next month because of it
Instrumentation, funnels, and the discipline of measuring the same thing the same way.
- Technical search optimisation, structure, and content that answers real queries
- Paid campaigns with tracked spend and attributed outcomes
- Analytics instrumentation and funnels measured consistently
- Landing pages, onboarding flows and the removal of steps that lose people
- Lifecycle: email, notification and retention work after acquisition
Drawn from the same material that built our own products, not from a generic syllabus.
- Backend engineering: architecture, data modelling, APIs, testing
- Frontend and mobile engineering
- Cloud, deployment and operations
- Security fundamentals for engineering teams
- Product management and technical writing
- Curriculum design and delivery for institutions
For clients who want the system run rather than handed over.
- Day to day running, monitoring and incident response
- Dependency updates, security patching, small enhancements
- A named channel with agreed response and resolution targets
- Monthly service reporting against those targets
- Ongoing development against an agreed backlog
More than thirty external integrations in production or in build, which means most client integration work is something we have done before.
- Feature code never imports an integration; providers normalise into contracts
- A payment provider, broker or data source can be replaced without touching features
- Non critical asynchronous work is enqueued rather than awaited
01 / 16
Software and platform engineering
The core of the practice. We build backend systems, application programming interfaces, web applications and mobile applications, and we operate them afterwards if that is what the client needs.
- An explicit data model where every record carries its owner
- Role based access control, configured per organisation rather than hardcoded
- An audit trail that records who did what, when, and under what authority
- Background job processing with retries and dead letter handling
- Notification across in application, email, SMS and push
- Reporting that reads from the same data the application writes
- Documentation good enough for a different team to take over
03Our products
Seven platforms we run, support and pay for
A services company that has never carried a product to market has never had to live with its own decisions. Our products are where the doctrine gets tested.
Why we build our own
They fund the practice, prove the platform, and give clients something concrete to look at rather than a list of claims. We run them, support them, and pay for every shortcut we take.
Licensing and white label
Each platform can be licensed, deployed privately, or white labelled under your own brand.
The fastest route to working software
Where a requirement is close to a product we already run, that is usually the cheapest path.
ErasCare
Health
34
modules
Patient controlled healthcare platform
A patient controlled healthcare platform connecting patients, families, verified independent practitioners, healthcare organisations, health data, connected devices and health plans. Every relationship is an explicit, permission controlled, auditable record.
ErasTrade
Finance
36
modules
Non custodial multi currency financial application
Multi currency wallets, card issuance and funding, transfers, foreign exchange, and access to markets in equities, crypto and foreign exchange. Licensed third parties hold and move the money; ErasTrade orchestrates and records, on a double entry ledger that is the source of truth.
ErasPay
Payments
New
in the group
Payment application for collection, transfer and settlement
A payments application covering collection, transfers and settlement, built on the same ledger discipline as the rest of the group: money movement is orchestrated and recorded, and balances are derived from the ledger rather than stored against an account.
SkulHive
Education
28
modules
Lifelong academic operating system
One identity follows a person from admission to retirement, carrying learning artifacts, communities, timeline, portfolio and opportunities. It is deliberately not a university management system; it holds the part no institution has a reason to keep.
Quint
Employment
AI
career agent
AI career agent and two sided marketplace
It discovers relevant roles, understands a candidate's professional profile, matches the two, prepares job specific application materials, applies within rules the candidate sets, and tracks the journey through to offer.
KMS
Enterprise
14
design parts
Modular multi tenant business operating platform
A business installs only the plugins it needs and pays for what it uses. One hierarchy, tenant to organisation to company to branch, serves every industry, so a new vertical is a preset of existing plugins rather than a new product.
MUUV
Travel
20
categories
B2B travel infrastructure API
One integration lets a business sell every category of travel, from flights, hotels and transfers to activities, insurance and connectivity, across the supply behind them. MUUV does not sell to travellers and does not compete with its customers.
04How we work
Four phases, each with a defined output
A structured approach to designing, building and delivering software systems, so nobody has to guess what is happening or what happens next.
01
AnalyseDiscover
We analyse your requirements, understand your business context, and identify the right technology approach.
We spend the first phase making sure the thing being built is the thing that is needed, talking to the people who will use it, reading the process as it actually runs rather than as it is described. Uncertainty named at this stage is manageable. Uncertainty discovered in month four is not.
Output
A written scope, a risk list and a recommendation.
02
ArchitectDesign
We architect your system, define technical specifications, and plan the full development lifecycle.
Architecture, data model, access model and interface design, decided together because they constrain each other. We also decide the build order here, which matters more than it sounds: building in the wrong order is how projects arrive at eighty per cent complete and stay there.
Output
Data model, architecture, interface design and a build order.
03
EngineerBuild
We engineer your solution using modern technologies, clean practices and rigorous quality standards.
Delivered in increments you can review, not in one long silence followed by a reveal. Each increment is working software against the agreed scope, with tests, and with the documentation written as it goes rather than at the end.
Output
Working software, delivered in reviewable increments.
04
Hand overDeliver
We deploy, test and hand over your system with full documentation and ongoing support.
Deployment, verification, handover documentation, and training for the team that will operate it. Where we continue to run the system, the handover still happens, because a client who cannot leave is not a client we want.
Output
A running system your team can operate.
Engineering doctrine
The same rules apply in every repository we own or take over. They are the reason a small practice can maintain a large portfolio.
01
Ownership is explicit
Every business record carries its owner. Nothing is scoped implicitly and nothing important is inferred.
02
The ledger is the truth
Where money moves, a transaction, a ledger entry and an audit record are written together. Balances are derived, never authoritative.
03
One abstraction seam
Feature code never talks to a third party directly. Integrations normalise into contracts, and features consume the contract.
04
API first
Every feature in an application is reachable through the API. The application is just another consumer of it.
05
Permission over relationship
A relationship is not a permission. Access is granted, recorded, time boxed and revocable.
06
Provenance preserved
Every measurement, record and generated document carries who or what produced it, and how.
07
Audit is a first class object
Consent, authorisation, access grant, actual access and audit event are separate records, not one log line.
08
Configuration over code
A rule that varies between customers is configured, never forked into a branch of the source.
Standards
What we hold ourselves to, on every repository
A working session each week, a written summary whether or not anything went wrong, a shared board showing what is in progress and what is blocked, and a named contact on both sides.
- Source controlEvery change reviewed before it merges; history preserved
- DocumentationArchitecture, API and operational documentation live with the code
- TestingAutomated coverage on business critical paths, not on trivia
- SecretsNever in source control, rotated, scoped to environment
- DependenciesTracked, updated, and reviewed for licence and security risk
- MigrationsEvery schema change reversible and applied the same way everywhere
- ReleasesRepeatable, automated, and safe to roll back
- AccessLeast privilege, reviewed, and revoked when an engagement ends
05Technology
One set of foundations, under everything we build
Seven products and a services practice run on the same platform. A new engagement starts from working components rather than an empty repository.
- Identity
- Access
- Audit
- Payments
- Notification
- Storage
- Reporting
- Jobs
The stack
12 layers- ServicesNode.js with TypeScript
Fast to build, typed, huge ecosystem
- High throughputGo
Where concurrency and latency decide the design
- DataPostgreSQL
Transactions, constraints, and a query planner we can reason about
- Vector searchpgvector
Semantic search without a second datastore to operate
- Cache and queueRedis with a job runner
Background work with retries and dead letter handling
- Real timeSocket based messaging
Live updates that survive more than one server
- WebNext.js and React with Tailwind
Fast pages, a component discipline, and good defaults
- MobileReact Native and Expo, Flutter where it fits
One codebase where that is honest, native where it is not
- IdentityJWT with server sessions, WebAuthn, TOTP
The database, not the token, is the source of truth
- AIModel routed through a provider gateway
Never hard wired to one vendor
- StorageS3 compatible object storage
Portable across providers and regions
- ObservabilityStructured logging with audit trails
Questions answerable after the fact
| Layer | Choice | Why |
|---|---|---|
| Services | Node.js with TypeScript | Fast to build, typed, huge ecosystem |
| High throughput | Go | Where concurrency and latency decide the design |
| Data | PostgreSQL | Transactions, constraints, and a query planner we can reason about |
| Vector search | pgvector | Semantic search without a second datastore to operate |
| Cache and queue | Redis with a job runner | Background work with retries and dead letter handling |
| Real time | Socket based messaging | Live updates that survive more than one server |
| Web | Next.js and React with Tailwind | Fast pages, a component discipline, and good defaults |
| Mobile | React Native and Expo, Flutter where it fits | One codebase where that is honest, native where it is not |
| Identity | JWT with server sessions, WebAuthn, TOTP | The database, not the token, is the source of truth |
| AI | Model routed through a provider gateway | Never hard wired to one vendor |
| Storage | S3 compatible object storage | Portable across providers and regions |
| Observability | Structured logging with audit trails | Questions answerable after the fact |
Hosting and data residency
- Default
- Regional hosting, with data held in the client's own jurisdiction
- Regulated data
- Health and financial data stays in country by design
- Separation
- Development, staging and production isolated, with controlled data flow
- Backup
- Automated, encrypted, with restore rehearsed rather than assumed
- Continuity
- A documented recovery plan with a stated recovery objective
- Exit
- Client data exportable in an open format, on request, without a fee
Languages and platformsNo single stack
The table above is what we reach for first on a greenfield build. It is not the limit of what we work in. Most engagements involve an estate that already exists, so we work in whatever it is written in.
Languages
- TypeScript
- JavaScript
- Python
- Go
- Java
- C#
- PHP
- Kotlin
- Swift
- Dart
- Rust
- SQL
Backend and services
- Node.js
- NestJS
- .NET
- Spring Boot
- Django
- FastAPI
- Laravel
- gRPC
- GraphQL
- REST
Frontend and mobile
- React
- Next.js
- Vue
- Angular
- React Native
- Expo
- Flutter
- SwiftUI
- Jetpack Compose
Data and storage
- PostgreSQL
- MySQL
- SQL Server
- MongoDB
- Redis
- pgvector
- ClickHouse
- Elasticsearch
- Kafka
- S3
DevOps and cloud
- Docker
- Kubernetes
- Terraform
- Ansible
- GitHub Actions
- GitLab CI
- AWS
- Azure
- Google Cloud
- Nginx
- Prometheus
- Grafana
AI and machine learning
- LLM gateways
- Retrieval augmented generation
- Embeddings and vector search
- PyTorch
- TensorFlow
- scikit-learn
- Document extraction
- Computer vision
- Speech to text
Architecture patterns
MODULES/{NAME}/
- ├──interfacerepository and service contracts, input and query types
- ├──modelone file per entity
- ├──repositorydata access, transaction aware
- ├──servicebusiness rules, owns transactions
- ├──controllerthin, no logic
- ├──validatorsa schema per operation
- └──routesvalidation, auth, access control, handler
Every module in our codebases has the same shape. It is what keeps dozens of them maintainable by a small team, and what lets a new engineer be useful in days rather than weeks.
The request path
Non critical asynchronous work is enqueued rather than awaited, so a slow third party cannot hold a user's request open.
The integration seam
That is what lets a payment provider, a broker or a data source be replaced without touching the features that depend on it.
Integrations we already operate30+ in production or in build
Payments and collection
Card tokenisation, charge, 3D Secure, settlement, payouts
Card issuance
Virtual and physical card programmes
Identity verification
Document and biometric know your customer
Brokerage and markets
Equities, crypto, foreign exchange, market data
Communications
Transactional email, SMS, push notification
Authentication
Federated sign in across the major identity providers
Real time media
Video and audio calling, live streaming
Travel supply
Flights, hotels, transfers, activities, insurance, eSIM
AI
Model gateways, embeddings, document extraction
Storage and media
Object storage, image and video pipelines
Payments and collection
Card tokenisation, charge, 3D Secure, settlement, payouts
Card issuance
Virtual and physical card programmes
Identity verification
Document and biometric know your customer
Brokerage and markets
Equities, crypto, foreign exchange, market data
Communications
Transactional email, SMS, push notification
Authentication
Federated sign in across the major identity providers
Real time media
Video and audio calling, live streaming
Travel supply
Flights, hotels, transfers, activities, insurance, eSIM
AI
Model gateways, embeddings, document extraction
Storage and media
Object storage, image and video pipelines
06Industries we serve
Not industry agnostic, we have built here before
We have built real systems in these sectors and carry the domain knowledge that comes with that.
Healthcare
Clinical records, consent and access control, practitioner verification, appointments, pharmacy and laboratory workflows, health programmes.
Financial services
Ledgers, wallets, cards, payments, reconciliation, know your customer, market access, and the audit trail regulators expect.
Education
Academic identity, institutional structure, learning resources, communities, credentials and the transition into employment.
Employment and recruitment
Job ingestion, profile parsing, matching, application tracking, employer pipelines and hiring analytics.
Enterprise operations
Multi entity hierarchies, permissions, approvals, finance, inventory, point of sale, human resources and usage based billing.
Travel and mobility
Supplier aggregation, booking lifecycles, multi currency settlement, credit lines and reconciliation.
Public sector
Registries, identity, workflow, oversight reporting and data residency.
Retail and commerce
Catalogues, orders, payments, fulfilment and customer records.
Logistics
Movement, dispatch, tracking and the settlement that follows it.
Media and creative
Publishing systems, content operations, audience analytics.
Non profit and development
Beneficiary records, programme reporting, donor accountability.
Where we have not built before
We do not pretend otherwise. What transfers is the part that is the same everywhere: the data model, the permission model, the audit trail, the integration discipline and the delivery process. The domain we learn from you, in discovery, and we write down what we learned so it can be checked.
07Working with us
Different problems need different commercial shapes
These are the ones we use. Discovery is chargeable and is worth paying for. An engagement that skips it is an engagement where the price is a guess.
Project delivery
A defined scope, a fixed timeline and an agreed price. Best where the requirement is clear and the outcome is a specific system.
Priced from the scope agreed in discovery, with a written change process.
Retained team
An agreed monthly capacity working an evolving backlog. Best where the requirement will keep changing and speed matters more than a fixed scope.
A monthly fee for an agreed capacity, reviewed quarterly.
Dedicated squad
A named team working only on your product, embedded in your process. Best for sustained multi quarter product development.
Priced per role per month, with a minimum term.
Build, operate, transfer
We build and run the system, then hand it to your own team with the documentation and training to take it over.
Blended build and operate terms, agreed per phase.
Advisory and audit
Time bounded engagements producing a written assessment and a plan, with no obligation to build afterwards.
Day rate or fixed fee for a defined deliverable.
Licence and white label
Deploy one of our platforms under your own brand instead of building from zero.
Annual, by deployment and usage.
On every engagement
What you get, whether or not we stay
- A named contact who is accountable for delivery, not a rotating queue
- A written scope, and a written record of every change to it
- Working software you can review in increments, not one reveal at the end
- Source code in your own repository, under your ownership
- Architecture, API and operational documentation written as we go
- Handover and training, whether or not we continue to operate the system
- A support window after delivery, with defined response targets
Intellectual property
Unless we agree otherwise in writing, everything we build for you under a paid engagement is yours: source code, designs, documentation and data. That boundary is written into the contract rather than left to be discovered later.
Monthly reporting against the plan, in language a non technical sponsor can act on.
Service levelsSet per contract
- Critical
Production down or data at risk
- Response
- 1 hour
- Resolution
- Continuous until resolved
- High
Major function unusable, no workaround
- Response
- 4 hours
- Resolution
- 1 business day
- Medium
Function impaired, workaround exists
- Response
- 1 business day
- Resolution
- 5 business days
- Low
Cosmetic or minor
- Response
- 2 business days
- Resolution
- Next release
Targets apply within the agreed support window. Where a client needs cover outside business hours, that is priced explicitly rather than assumed.
Why clients choose us
We have built this before
More than 150 engineered modules and 30 production integrations across seven sectors. Most requirements are not new to us.
We are a registered, verifiable company
Publicly verifiable registration, tax identification and a maintained corporate record, for organisations that must check.
We build to be handed over
Documentation, tests and clean handover are part of delivery, not an upsell. A client who cannot leave is not a client we want.
We do the unglamorous parts
Data models, permissions, audit trails and reconciliation. They are what decides whether a system is still usable in year three.
We say the difficult thing early
If the plan will not work, we say so before it is built, with an alternative.
One partner, several disciplines
Engineering, design, content and advisory under one agreement, rather than three vendors blaming each other.
08Governance and trust
A registered, verifiable company
Businesses in this market are routinely asked to prove they exist before they can be engaged. Our registration, tax identification and public record are maintained precisely so that question is answered in one step.
The corporate record
Active- Legal name
- ERASSTACK LTD
- Registration number
- RC 9385639
- Date of registration
- 3 March 2026
- Company type
- Private company limited by shares
- Governing act
- Companies and Allied Matters Act 2020
- Status
- Active
- D-U-N-S number
- 352295718
- Verification
- Corporate Affairs Commission public register
- Business verification
- Dun & Bradstreet verified
Governed by its board of directors, with a company secretary appointed under the Companies and Allied Matters Act.
Security and data protection
Standing commitments
Our products hold clinical records, financial ledgers, academic identity and employment history. The posture is a set of standing commitments rather than a feature list.
- Role based access, subscription entitlement, resource access and consent are separate systems. The backend is authoritative for all of them.
- Sessions are recorded per device and location. New device and new location logins raise an alert with a revoke path.
- Personal data is encrypted at rest where it is held, and in transit everywhere.
- Data residency is regional by default. Health and financial data stays in country.
- Every access to a sensitive record produces an audit event tied to the authority that permitted it.
- Client data is used for the client's purposes only. It is not reused, aggregated across clients, or used to train models.
What we will not do
We do not fabricate data on a user's behalf. We do not bypass authentication, CAPTCHA or anti bot protections. We do not scrape sources where the activity is prohibited. Where a system acts for a person, it acts within rules that are written down and enforceable.
Compliance
Corporate
Statutory filings, annual returns and register maintenance kept current with the Corporate Affairs Commission.
Tax
Registered for tax with a tax identification number, and compliant with applicable filing obligations.
Data protection
Personal data handled under the applicable Nigerian data protection regime, with consent, retention and access rights treated as design requirements.
Contractual
Written agreements covering scope, confidentiality, intellectual property, data handling and liability on every engagement.
Confidentiality
Client information is confidential by default, not on request. We sign non disclosure agreements, we scope access to the engineers actually working on an engagement, we revoke access when the engagement ends, and we do not name a client publicly without written permission.
Business continuity
- Code
Every repository mirrored, with history preserved
- Knowledge
Architecture and operational documentation written as work happens
- Access
No single person holds sole access to any system we operate
- Backup
Automated and encrypted, with restore tested rather than assumed
- Succession
Engagements are staffed so no single departure stops delivery
Social impact
Structured pathways for junior engineers and designers, including people without a formal computer science background. And products built for the reality here: intermittent connectivity, low end devices, and users who cannot assume a card.
09Common questions
The questions we get asked first
Discovery can usually begin within one to two weeks of an agreement. Build capacity depends on the shape of the team required and is confirmed during discovery rather than promised beforehand.
Yes. We work remotely as standard, with an agreed overlap window for the client's working hours.
You do. Everything built for you under a paid engagement is yours, including source, designs and documentation. Our pre existing components remain ours and are licensed to you as part of the delivery.
Yes, and it is a significant part of the practice. We start with an audit that tells you honestly what you have, what it will cost to stabilise, and whether continuing is the right call.
Yes. Embedded delivery alongside a client team is one of our standard models, including the training that makes the handover real.
Advisory and audit engagements are deliberately separate from build work, and carry no obligation to build afterwards. An assessment you cannot act on independently is not worth paying for.
Under written agreement, with scoped access, encryption at rest and in transit, regional residency where required, and revocation when the engagement ends. Client data is never reused across clients or used to train models.
Yes. We work with agencies, resellers, technology vendors and institutions, including licensing or white labelling our own platforms. Tell us the shape you have in mind and we will reply within one business day.
How to start
- 01
Get in touch
Email or message with a short description of what you are trying to achieve. We reply within one business day.
- 02
Introductory session
A conversation, at no cost, to understand the problem and decide whether we are the right people for it.
- 03
Proposal
A written proposal covering approach, scope, timeline, commercial terms and assumptions.
- 04
Discovery
The first paid phase, producing the scope and the plan the rest of the work is built on.
10Contact
Tell us what you are trying to achieve
A short description is enough to start. We reply within one business day, and the introductory session that follows costs nothing.
Direct channelsOpen
WhatsApp+234 703 806 3828Fastest route to a person- Emailsupport@erasstack.comBest for a written brief or an RFP
- Phone+234 703 806 3828Business hours, West Africa Time
Partnerships welcome. We work with agencies, resellers, technology vendors and institutions, including licensing or white labelling our own platforms. Choose Partnership on the form and tell us the shape you have in mind.