Create a single pane of glass for your business.
Portals, APIs & Marketplaces are how people see and work with what your business does. The portal faces your customers, or your own operations. The API beneath it reaches further: your customers integrate it into their own product portfolios and systems.
We can advise on the experience or build and run it if you want us to.
A public API, on an open standard. For a major African interconnection platform we shipped a new public API on an open standard, with a partner sandbox to build against. It is the experience layer over the platform beneath it.
Every status check is a ticket. Every invoice question is a wait.
Your customers cannot see their own services without raising a ticket. Every status check, usage query and invoice question lands on your team, and every one is cost to serve and a customer kept waiting. Inside, your own people are no better served: rack and asset information lives in isolated tools or spreadsheets, so a simple question means asking multiple people. The experience of being your customer is part of the product, and so is the work behind it.
A portal puts services, usage, tickets and invoices in front of your customers, and asset and operations data in front of your team, at any hour, without anyone in the loop. It shows them what they have. When you are ready to let them order and provision on demand, that is the front door the Self-Service Infrastructure and Network-as-a-Service solutions open through.
Buy a product, or build the one you own.
Buying a portal is the fast path: pick a product and switch it on. The cost shows up later. You rent it for as long as you run it, shape your operation to fit its data model, and wait on someone else’s roadmap for what it does next. It is built for the vendor, and you never own it.
We build yours instead, onto the systems you already run and to the shape of your business, then hand over the source and the IP. It takes longer than switching on a product. In return you own an asset that fits, that your team can change without us, and that stops billing you the day you stop needing us.
A single pane of glass, and the API beneath it.
This block is the experience layer. It exposes what your platform can already do. The portal flexes to face your customers or your own operations, and there is always an admin side behind it for the team that runs it. We build it API-first, or onto the CRM or ERP you already run. On one engagement it shipped as a new public API on an open standard, with a sandbox partners build against.
A portal that faces whichever way you need, customer-facing for services, usage, invoices and tickets, or internal for asset and rack information, with role-based access for the teams that use it.
A documented, versioned API, built to the MEF LSO APIs (Cantata for your customers, Sonata for wholesale partners), that your customers and partners integrate against, so your services become programmable.
Services, usage and billing visible and queryable without raising a ticket, in the portal and over the API.
Authentication, accounts and entitlements so the right customer sees the right services and pricing.
Build your own marketplace, in your brand: a storefront and catalogue where your customers and partners discover what you and they sell, yours to run rather than a listing on someone else's platform.
An admin side behind every portal where your own team manages accounts, entitlements, content and the records the portal shows, so the people running it are not locked out of their own tool.
An optional knowledge base inside the portal, so guides, documentation and answers sit where customers and staff already are, and fewer questions become tickets.
The experience layer, delivered.
- Customer portal
- Branded, role-based, in production
- Developer API
- Documented and versioned, on the MEF LSO APIs (Cantata, Sonata)
- API contract
- The machine-readable spec that drives docs, tests and client libraries
- Partner sandbox
- A production-like environment partners build against
- Identity & accounts
- Authentication, roles and entitlements, with SSO federation
- Integration to the platform beneath
- The seams wiring portal and API to OSS/BSS, catalogue and network so services, usage and invoices are real and current
Full specifications travel in proposals.
A block on its own, or part of a larger platform.
Buy it on its own, or as one layer inside a full transformation.
Advise, build and run. Take all three, or only what you need.
We advise. You build.
The experience and the API contract, so your team builds the right front door.
We build and deliver.
The portal, the API and the catalogue, integrated with the platform beneath them.
We run it.
Operated in production, or handed to your team to run.
You own the IP we build together. The source code is yours: no product licence, nothing to renew, nothing phoning home. Run is offered, not required: we operate it for you, or hand it to your team. Your leverage grows as you own and extend the asset, instead of compounding inside a platform you rent. Advise, build and run is a choice, not a dependency.
Your services, in their hands.
Tell us how your customers work with you today. We will map the experience layer, and what it is worth.
