Design and spec
The drawing on the canvas. Sizes, finishes, hardware. The one place a number is entered.
sourceVeloxa Technology Ltd · Accra, Ghana · software engineering
Run your business like it’s twice the size.
We build the operations platforms, internal systems and AI agents behind Africa’s fastest-moving teams. Here is what that actually means, running.
Quoting
Customer, price list, the quote that actually goes out the door.
re-key: 9 fieldsFactory floor
The cutting plan the saw runs, and the pack the fitters carry.
re-key: 11 fieldsStock and ERP
Profile, glass and hardware taken off stock against the job.
re-key: 8 fieldsAccounting
The invoice, matched to the quote to the pesewa.
re-key: 7 fieldsCustomer, on WhatsApp
The order status the customer actually reads.
re-key: 7 fields0+Systems in productionShipped and running inside real businesses, not demos.
0+Countries servedClients across Africa and abroad, async-first.
0+Professionals trainedThrough hands-on AI and automation workshops.
0Month of discoverySpent on the factory floor before any code was written.
The state most businesses are in
Six systems. One business. None of them talking.
Nothing here is broken. Every one of these tools does its own job well. The cost is in the gaps between them, where a person reads a number off one screen and types it into the next, and where the same order quietly becomes six slightly different versions of itself.
| System | What it holds | Fed by hand |
|---|---|---|
| Design and spec | The drawing on the canvas. Sizes, finishes, hardware. The one place a number is entered. | source |
| Quoting | Customer, price list, the quote that actually goes out the door. | 9 fields |
| Factory floor | The cutting plan the saw runs, and the pack the fitters carry. | 11 fields |
| Stock and ERP | Profile, glass and hardware taken off stock against the job. | 8 fields |
| Accounting | The invoice, matched to the quote to the pesewa. | 7 fields |
| Customer, on WhatsApp | The order status the customer actually reads. | 7 fields |
| Total, per order | Read off one screen, typed into the next. | 42 fields |
Before anything is built
We learn the business before we build for it.
On our most recent manufacturing engagement that meant a month on site, following the work: watching a quote get written, watching a cutting list get carried to the saw, watching the same dimensions get typed a fourth time.
We ask for documents rather than descriptions, because a real invoice answers ten questions truthfully and a meeting about invoices answers none of them. Only then do we propose a system, in writing, with the scope fixed before anyone commits.
One source. Everything else derived.
Keep scrolling. The six systems wire together, one order is pushed through, and every figure below is worked out from it. Nothing is typed twice.
board veloxa / opssample scenario · figures computed livelinked 0 of 5manual re-keys 42
Design and spec
The drawing on the canvas. Sizes, finishes, hardware. The one place a number is entered.
—Quoting
Customer, price list, the quote that actually goes out the door.
—Factory floor
The cutting plan the saw runs, and the pack the fitters carry.
—Stock and ERP
Profile, glass and hardware taken off stock against the job.
—Accounting
The invoice, matched to the quote to the pesewa.
—Customer, on WhatsApp
The order status the customer actually reads.
—operate itquantity34Change either one. Every figure on the board recomputes.
Already shipped
Hiring infrastructureSix things we have already built and run.
Each one started as somebody’s manual process. Each one has its own page.
VeloxaRecruit
Automated CV screening and multi-modal interviews, running end to end.
Open →Candidate experienceSmartMatch
Role recommendations and tailored CV generation for the person applying.
Open →GrowthLeadGen AI
Prospect identification and qualification driven by behaviour, not lists.
Open →SchedulingTelegram Booking
Appointments taken in chat, written straight into Sheets and Calendar.
Open →CommerceWhatsApp Food
Orders taken by an agent, menu links sent, receipts returned in the thread.
Open →PrototypingDemoForge
A working demo of your idea, built before anyone commits to production.
Open →And the ones that are yours alone.
Most of our work never becomes a product. It is the platform one business runs on, built for how that business actually works.
Talk about yoursWork you can inspect
Engagements, written up in full.
Each one is a complete account of what we found, what we decided and what we built, including the parts that were harder than expected. Open one and read it end to end.
One month on the factory floor before a line of code
A manufacturer was one signature away from buying a foreign off-the-shelf ERP. We asked for a month inside their business first. What we found on that factory floor is the reason the software fits the way they actually work.
Workflow discovery + full platform buildIn production use
Most of our work sits under an active engagement and is not published. We can talk through those in a call, and name references where the client has agreed to it.
The unglamorous engineering, switched on by default.
You own the code, the data and the infrastructure
Repositories, cloud accounts, databases and documentation are yours from day one, handed over with training for the people who use the system daily. There is no lock-in to us.
on since day oneApprovals are gated, not assumed
Only the current revision of a drawing can be approved, and only an approved revision can reach production. The system refuses the wrong version rather than trusting somebody to notice.
enforced in softwareEvery artifact carries an integrity check
Files are checksummed when they are produced and verified when they are used, so a quietly corrupted or swapped document is caught before it costs a production run.
sha-256, every fileSuperseded work stays visible, and stamped
Old revisions are never silently deleted. They stay in the record, clearly marked, so the history of a decision survives the person who made it.
audit trail retainedThe questions buyers actually ask.
Do you only build AI, or software in general?
We are a software engineering company. We design and build full production systems: operations platforms, internal tools, customer-facing products, integrations, data pipelines. We put AI inside them where it genuinely earns its place. A configurator, a quoting engine or a gated factory pipeline is not an AI problem, and we will tell you so rather than sell you a model you do not need.
Do you only work with large companies?
No. We work with startups, SMEs and established manufacturers and service businesses across Africa and globally. What matters is that you have a real problem and the budget to solve it properly, not the size of your org chart.
What does an engagement typically look like?
Most start with a discovery call, then a fixed-scope build or an ongoing retainer. Smaller builds run two to six weeks; platform work runs longer and ships in weekly increments you can use as they land. Deliverables are defined upfront in writing, so there is no scope creep and no surprise invoices.
Can you work with the systems we already have?
Yes, and most of our work is exactly that. Integrating with an existing ERP, accounting package, CRM or WhatsApp channel is usually the point. We would rather extend what your team already knows than force a migration nobody asked for.
Who owns the code, the data and the infrastructure?
You do, outright, from day one. Repositories, cloud accounts and databases are yours, handed over with documentation and team training at the end of the engagement. You are never locked into us to keep your own system running.
How do you approach a workflow you have never seen before?
We learn it before we build for it. On a recent manufacturing engagement that meant a month on site: following the work, collecting real documents instead of descriptions, and only then proposing a system. It is why the software fits the business instead of the business bending to the software. The full account is on our case study page.
Do you train our team as well?
Yes. Every handoff includes documentation and hands-on training for the people who will use the system daily. We also run practical AI and automation workshops for business teams in Ghana and remotely, built around your actual tools rather than a generic curriculum.
Where are you based, and can you work with us remotely?
Veloxa is based in Accra, Ghana, and we work with clients internationally, async-first. For engagements where being physically present changes the outcome, such as factory floors, warehouses and clinics, we show up in person.
Open a thread
Tell us what is being retyped.
That is usually enough to start. Name the systems you run and the step that still happens by hand, and we will come back with what we would do about it.
John Evans Okyere
Founder · Veloxa Technology Ltd, Accra
Accra, Ghana · working async with clients worldwide