Modules activated
The product core is mandatory. Beyond it you license only what you turn on — and modules can be scoped to particular entities, processes or document types rather than the whole organisation.
Commercial model
Licensed by module. Quoted to your estate.
We do not publish a per-user price, and you should be wary of anyone in this category who does. A control platform's cost is driven by how many entities and sites it governs, how many source systems it has to speak to, how many documents pass through it, and whether it runs in our environment or yours. Those vary by an order of magnitude between customers.
What a quote depends on
Five variables, and none of them is seat count.
Organisational scope
Legal entities, business units, branches and receiving locations. A single-entity deployment and a fifteen-entity group are different products in everything but the code.
Document volume
Invoices, orders, delivery notes and receipts passing through intake and document AI. Volume drives infrastructure and the OCR path more than it drives anything else.
Deployment profile
Multi-tenant SaaS, dedicated private cloud in your account, or on-premises. Each carries a different operational responsibility split, and the commercial model follows that split.
Adapters & certifications
How many source systems, and whether any tax-authority integration requires certification — KRA vetting, RRA certification, Nigerian APP or UAE ASP accreditation each have a real lead time.
Implementation
Discovery, configuration, adapter build, data migration, supplier onboarding and change management are scoped and priced separately from the licence. We would rather show you a bottom-up number than a percentage.
Before you commit
We scope with a paid discovery phase and a go/no-go gate.
Accounts-payable automation programmes fail in predictable ways: suppliers who never adopt the portal, a vendor master too dirty to match against, an ERP integration that turns out to be a rebuild, a tax-authority certification nobody put in the plan. Every one of those is knowable before a build commitment — if someone looks.
So the first engagement is a scoped discovery phase that produces a bottom-up effort estimate, a supplier-readiness survey, an integration and data-quality assessment, and a documented go or no-go decision. It can conclude that you should not proceed. That is a real outcome, not a formality, and it is far cheaper here than in month four.
Discuss a discovery phaseWhat discovery produces
Bottom-up effort estimate
Built from the actual scope, not a template. With the assumptions written down so you can challenge them.
Supplier-readiness survey
Your top suppliers classified as self-service-ready, assisted, or not ready — with a pilot cohort named.
Source-system and data assessment
What your ERP can actually expose, and how clean the vendor master and item master really are.
Compliance and certification plan
Which regimes apply to which entity, and the lead time on every certification in the path.
A go or no-go recommendation
With the conditions attached to a "go", so nobody discovers them later.
Procurement route
AWS Marketplace — listing in progress.
We are listing Procure-to-Pay Platform on AWS Marketplace as a container product, with a companion professional-services listing for implementation, configuration and adapter work. A container listing is the right shape for this product because it deploys into your own account and VPC rather than ours.
When it is live, the practical benefits for your procurement team are real:
- Transact against your existing AWS agreement rather than opening a new vendor relationship
- Use the Standardized Contract for AWS Marketplace, reducing bespoke legal review
- Custom terms and pricing through a private offer where a public listing does not fit
- Where you hold an AWS Private Pricing Agreement, Marketplace spend typically draws down your committed spend — subject to the terms of your specific agreement
Two things we will not overstate. First, the listing is in progress, not live —
today the route is a direct contract with CloudTech Crafters Limited. Second, commitment
drawdown rates and caps are set in your own AWS agreement, not by us; confirm the specifics with
your AWS account team rather than taking a vendor's word for it. On-premises deployments cannot
be metered through Marketplace and remain a direct contract.
Routes to purchase
| Route | Status |
|---|---|
| Direct contract with CloudTech Crafters Limited | Available now |
| AWS Marketplace — container product | In progress |
| AWS Marketplace — professional services | In progress |
| AWS Marketplace private offer | On listing |
| Channel partner private offer | On listing |
| On-premises licence | Direct only |
CloudTech Crafters Limited is a cloud and software engineering firm operating from Nairobi.
Where the product is
We are selecting design partners for the first deployments.
Being straight about this is worth more to both of us than a page of invented logos. The product core, matching engine, supplier collaboration and receiving capability are built to a defined specification with published acceptance gates. It is early, and the first customers are design partners rather than references.
What a design partner gets
- Direct influence over the roadmap in your industry profile
- Reference-customer commercial terms, agreed in the contract
- Senior engineering attention that a later customer will not get
- A configuration built around your process, not a template
What a design partner gives up
- The comfort of a long list of comparable customers
- Some tolerance for a roadmap that is still moving
- Time from your own AP, procurement and IT teams during discovery
- Willingness to be a reference later, if it goes well
If that is not you, say so early. Plenty of organisations should buy an established
product with fifty comparable references, and we would rather tell you that in the first
conversation than discover it together in month four.
Get a number that means something.
Bring your entity count, source systems and rough document volume. We will tell you what shape of engagement this is before anyone writes a proposal.