Portals, member directories, application reviews and the operations software your team lives in. Bilingual, mobile, no per-seat fee, and you own the code and the data.
The SPARK Innovation Hub: six weeks to launch, 500+ organisations, and a three-year partnership after it.
If an off-the-shelf tool does 80% of it, we will tell you which one on the call.
Six weeks is the SPARK Innovation Hub build, measured on that engagement rather than projected. Adoption figures — organisations onboarded, users migrated, concurrent load — sit with the client in section 9.
Three ways an organisation ends up running something important on software nobody chose.
It works because one colleague knows which tab is current and which formula lies. The process is not documented anywhere except in their habits, and the risk is not the file — it is their notice period.
A CRM doing membership, a project tool doing applications, a form builder doing intake. Each is 60% right, none talks to the others, and every gap is closed by somebody copying between them.
Quoted as an enterprise system, scoped for three years and cancelled in month eight. Nothing shipped, so nothing was learned — which is the expensive part.
The pattern is the same each time. The work is real and the software is borrowed.
Not "is the system slow". The call comes when a director asks how many applications are outstanding and the honest answer is that somebody will check.
Both are reading real data from real files. Neither is wrong, because there is no single record that either could be wrong about.
Most of it is learning where things actually live and which of the four documents is authoritative. That cost repeats with every hire.
A funder or a board needs figures, and producing them is a week of assembly rather than an export. The work bends around the report instead of the report reflecting the work.
Per-user pricing means every colleague, partner or member you add raises the bill before they have done anything. Success is charged for.
The approval flow that matters is the one the tool does not support, so it happens in email beside the system that was supposed to record it.
And the export is a CSV of the fields they chose to expose, without the relationships between them — which is the part that took years to accumulate.
Internal software is where bilingual support is quietly dropped, because the assumption is that staff will cope. Across this region a platform used by members, partners or applicants is used by people who will not cope, and will simply stop using it.
Navigation, tables, forms and every directional control mirror. A dashboard where the numbers still run left to right inside a right-to-left page is the tell that it was translated rather than built.
A partner filling in an application, a member updating a profile, a field officer logging a visit — none of them is at a desk. Internal does not mean desktop here.
Members and partners often have no organisational address. A one-time code to a phone is the difference between an account they can access and one they abandon at the first password reset.
Programme platforms answer to donors and boards with their own formats and cycles. Reporting is a build requirement, and retrofitting it means re-recording data you already had.
Usually the right question, and often the right answer is that you should buy it. Here is how we decide, in writing.
If something we built stops working the way it was specified, we fix it. No support contract required, no hourly rate, no argument about whose fault it is.
The guarantee lapses on code modified by a third party — the trade for owning it outright.
Buy the tool if it does eighty percent. Build when the twenty percent is the reason you exist.
Every line below ran on the SPARK Innovation Hub. The scaffolding is common to every platform of this kind; the workflow in the middle is the part that is yours alone, and it is where the time goes.
Platforms of this kind are eighty percent scaffolding — accounts, roles, forms, search, notifications. That part is known work. The remaining fifth is your process, and it is the only part nobody can estimate from a brief. So it goes first, while there is still budget to be wrong.
The approval, matching or scoring process drawn out end to end, including the exceptions people handle by hand today. Most of the disagreement surfaces here, which is where it is cheapest.
Only the part that is yours alone, working against real data, with no styling worth mentioning. You use it before we build anything around it.
Accounts, roles, directory, search, notifications and reporting. Known work, done fast, because the risky part is already proven.
Existing users and history moved with relationships intact, then load tested past the number you expect. Live at the end of it.
The scaffolding is known work. Your process is the only part nobody can estimate, so it is the part we build first.
Built for SPARK, the Dutch development organisation, as the platform where more than five hundred organisations across the Middle East and Africa find each other, publish opportunities and apply to them. Live in six weeks, and a partnership that has run three years since.
From Umbrella500_Canonical_Numbers.md — SPARK Innovation Hub Platform. The canonical file describes these as commercial-grade delivery proof even though the client was an NGO, which is exactly why they sit on a companies page.
The platform is at hub.spark.ngo , and is the one visual proof on this page you can check yourself today. Read the case study
SPARK is an organisation and this is a companies page. The build was a product delivery to commercial standards, which is how the canonical numbers file describes it, and we would rather say that than let a reader assume otherwise.
The people you meet on the call are the people who do the work.
Twenty years as a consultant and technology expert. Co-founder and COO of ShopGo, where she helped more than 1,000 MENA businesses scale online. She leads the technology practice and ran the Innovation Hub delivery.
Co-founder of ShopGo.me, acquired. He has supported over 13,000 entrepreneurs across the region and leads client relationships, including the three-year SPARK partnership that followed this build.
Most enquiries that reach this page should end in one of the first three columns, and we will say which on the call.
Right far more often than agencies admit.
Membership platforms, grant management systems and CRM suites solve most of this, immediately, with support attached. The cost is per seat and the process bends to fit theirs.
Choose it if: it covers eighty percent and the missing fifth is not the reason you exist.
Fast, cheap, and fine until it is load-bearing.
Airtable, Notion or a form builder wired together. Genuinely good for proving the workflow. The ceiling arrives at permissions, at reporting, and at the point where it holds data you cannot afford to lose.
Choose it if: you are still deciding what the process should be.
The right end state, at the wrong start.
A permanent team is better than any agency once the platform is the product. Hiring for it before there is a working system means paying salaries through the discovery phase, which is the least productive way to buy it.
Choose it if: the platform is your business and you have already proven it.
Costs more on day one. Costs nothing per seat, ever.
You own the code, the data and the process. No per-user fee, so growth stops raising the bill. The reference build reached real use in six weeks, and the workflow that made it worth building was running in week three.
Choose it if: the fifth no tool supports is the reason the organisation exists.
If an existing tool does eighty percent of what you need, we will name it on the call and tell you not to build. That happens more often than not.
Write down the one process that is genuinely yours — how you approve, match, score or award. If an existing tool supports it, buy the tool. If every tool makes you work around it, that is the case for building, and it is the only case we accept.
Yes, on the SPARK Innovation Hub, from start to real use with 200 migrated users. It is in Umbrella500_Canonical_Numbers.md against that engagement. Your timeline depends on how much of your process is genuinely unusual, and we will give you a range against it rather than repeat this number.
You do, on your infrastructure, in a standard PostgreSQL database. Not a hosted account we administer. If you leave, you keep the running system rather than an export of it.
Where it does a job you can name — matching applicants to opportunities, summarising a queue, answering from your own documents. We have built an assistant that operates a workflow rather than describing it, on a partner engagement. We will not put a chat box on a platform because it is expected.
Content, users, permissions and the reporting views, yes, without a developer. Changing the workflow itself is code, and you have the repository, the documentation and a standard stack so your own developer or another agency can do it.
We can, on a flat retainer, or your team can. The three-year code guarantee applies either way — defects, security patches and dependency updates on what we built are covered whether or not you retain us.
Tell us the one process that is genuinely yours and what you are running it on today. Thirty minutes, no cost, and we will name the tool to buy if there is one.
Or write directly: [email protected]