Invest in mojoh
If an enterprise brain existed, every enterprise would pay for one. mojoh’s path is to build it from ERP programmes they’re already funding.
- Wedge:ERP implementations where we capture shared SI solution knowledge as an enterprise model, then print migration, integration and test code directly instead of tying up engineers on repeatable plumbing.
- Moat:mojoh customers rapidly configure and absorb in-house / legacy apps and inter-app flows onto a graph-native enterprise memory layer with organic interconnections, so value compounds as more work moves onto it. Removing mojoh means rebuilding multiple tools plus the rich context between them, and losing that organic value.
- Upside:An enterprise brain that prioritises team activity from enterprise memory and amplifies productivity by guiding and automating initiatives while slashing “work about work”.
Why now?
Three shifts make mojoh's wedge urgent: cloud ERP programmes on the clock, a SaaS land grab to own the enterprise productivity stack, and a coming wave of autonomous agents that expect businesses to be machine-readable.
ERP mega-projects on the clock
Oracle, SAP and Microsoft cloud ERP moves are non-negotiable. They still rely on largely unguided solution configuration and hand-coded integrations and migrations that underwrite the SI "bums on seats" business model.
mojoh combines deep ERP knowledge and model-driven code printing with targeted AI to turn that work into captured SI skill encoded as information models, rules, mappings and guided flows you own. Those models print consistent deliverables instead of manual one-offs, cutting cost and risk on critical programmes. Over time that makes mojoh the trusted memory layer that new apps and workflows are built on as it grows into an enterprise brain.
Everyone wants to be your enterprise brain
Big SaaS vendors are in an arms race to be the place where work happens, retrofitting work graphs and "hubs" over external apps as their version of a brain. Teams still buy point solutions, so knowledge fragments and productivity erodes in context switching and duplicate work. AI then has to reverse-engineer basic context.
mojoh steps in as a trusted knowledge layer where humans and AI agents share the same enterprise brain. Information and processes are structured so agents propose and execute work while humans review, override and steer. Schema-aware apps and AI-infused workflows are configured on top, keeping that collaboration grounded in one common platform for work even as change across the enterprise accelerates.
Autonomous agents mediating enterprise work
Work is shifting from people clicking through apps and emails to agents proposing, negotiating and integrating within and between companies, with humans still in the loop for approvals and exceptions. To compete, a business has to expose what it knows and what it can do as governed, machine-readable capabilities — without waiting on IT to build another interface each time.
mojoh organises knowledge and interactions as a flexible graph exposed through a unified, self-extending, self-describing API, so internal and external agents can safely plug in even as the business changes. As the agentic era dawns, those agents increasingly self-serve against this enterprise brain, orchestrating interactions while humans stay in control.
Wedge → Land → Expand
Wedge: Start with the ERP project you’re already funding
You begin in a real ERP programme: migrations, integrations and cutovers. mojoh models the ERP solution, maps to and from source systems and enterprise apps, and prints migration, integration and test code from those mappings. That shared SI memory lives in mojoh as reusable enterprise knowledge instead of disappearing into decks and spreadsheets.
Land: Structure IT work and change on mojoh
After go-live, mojoh becomes the integration and change layer where you also organise IT work – the foundation of an eventual IT brain. When something changes, you update the model once and re-print interfaces and flows or configure new workflows and apps instead of commissioning new hand-coded modules. Delivery teams plan and track changes as model-driven work on mojoh, and gradually move logic out of scattered scripts and niche hand-coded tools and siloed apps into mojoh apps and tools that all sit on the same knowledge layer.
Expand: From IT brain to enterprise brain
Once the memory layer is in place, you add new model-driven apps, skills and transformations from mojoh and design partners on top of it – for finance, supply chain, customer, people and more. Each new app reuses and connects with the existing knowledge and provides new agentic reach, accumulating into an enterprise brain which guides work across the enterprise.
If an enterprise brain existed, every large enterprise would have to have one.
mojoh's path is to build that brain incrementally from programmes and pain they're already funding.
We land in implementation work, become the memory layer for integration, change and in-house apps, and expand into the enterprise brain.
Moat: mojoh capabilities that make this brain possible
Model-driven, self-constructing apps and pages
mojoh is model-driven end-to-end: information types, pages and apps are generated from the same knowledge model. That means we can extend mojoh's reach by configuration, rapidly mimic and integrate with existing apps (including their UI/UX patterns) and keep them in bi-directional sync – then, over time, swap them out. When we add or evolve a capability, we regenerate the code and it's available everywhere in mojoh.
Motes that can play many roles
Every mote inherits from its parent type, so extending an information type automatically extends all of its descendants. The same mote can be viewed or used as different roles – a customer, an account, a profit centre, a task – by projecting it into ancestor/descendant shapes or via mappings. Motes can move between roles over time without losing history, so different teams can use the same underlying facts in their own processes without duplicating data.
Graph-native motes and links
mojoh implements knowledge as graph-native motes and links: any mote can relate to any other via any relation, and those relationships are independent of the mote's current type. Motes can be transformed into other mote types – and back again – without breaking their links, so the graph survives change instead of being tied to one frozen schema.
Unified, model-driven API for everything else
A unified, model-driven API exposes the same knowledge graph to other apps and agents. We can integrate quickly by configuring information types and mappings (no custom glue code), and mojoh can self-describe to internal and external agents so they can safely read and act on enterprise memory.
The data network effect: what you’re betting on
Each design partner that extends the knowledge landscape enriches the shared graph and agentic reach. Each new transformation flow expands the tooling mojoh can access. The enterprise brain evolves, gets smarter and more irresistible with every small expansion. The same graph powers cross-domain insights, skills and agents that work across workflows, not just inside a single app — that’s the compounding data network effect you’re betting on.
Monetisation
Every programme and design partner extends the memory graph. Each new domain makes templates, flows and skills more reusable, so revenue comes from using that shared memory, not re-running the same project.
Platform + implementation work
Customers subscribe to mojoh as the delivery platform for their ERP programmes, with elfware and design partners delivering projects on top. Revenue today comes from this platform subscription plus implementation work: models, mappings, guided flows, printed code and data-quality flows for customer programmes.
Operating on the brain: seats, APIs and integrations
Unified APIs, events and agent-friendly access to the graph allows apps and agents to call mojoh as their brain, not each other. Monetisation shifts toward recurring platform fees with a mix of human seats in the apps and virtual seats for agents and integrations, with higher tiers unlocking more active virtual seats and domains.
Skills, templates and apps on the brain
Domain-driven templates, skills and apps built by mojoh and design partners all run on the same graph. Revenue expands to include marketplace fees, revenue share on partner-built skills, and enterprise licensing for private graph deployments.
Signals / traction
Early programmes on Oracle Retail and D365
80–90%
lead-time reduction
300+
pipelines in 2 weeks
< 1 day
time to value
3–10 days
toolchains delivered
Case studies
Oracle Retail CI/CD migration
Re-platformed 300+ pipelines from GoCD/BitBucket to Azure DevOps in 2 weeks with a single engineer.
Delivered at least 50% cheaper and faster (90% lead time reduction) than traditional methods.
D365 BC migration recovery
Project stalled after SIT due to data stream issues. In 2 weeks, deployed mojoh cell to automate raw-file → target loads with ~100 integrity checks.
Migration back on track, ≥6 months saved, with reusable templates for future Microsoft workloads.
Oracle Retail v11→v16 upgrade
3-day initial prototype, 2 weeks end-to-end automation. 100% reconciliation coverage.
Zero instability, full audit trails, no post-cutover issues.
Leadership
Operators who turn programs into products — faster, safer, governed.
Hamish Cameron
Founder & CEO
Unfair Advantage
- Founder-CEO who turns programmes into products: low-code, code-printing platforms + decision frameworks that standardise, accelerate, and de-risk delivery.
- Built a self-constructing knowledge graph and code-printed unified API enabling app delivery by config—add a schema, get an app; horizontal growth with near-zero incremental engineering.
- Capital-efficient: funded platform R&D through services, productising repeatable patterns into the core.
- Has undertaken virtually every role in an ERP implementation - programme director, solution architecture, technical build, data migration, integration, testing and support - giving first-hand insight into where time and money are wasted.
Proof Points
- • Delivered global transformation programmes; months → days build cycles.
- • Built the knowledge base + graph behind mojoh's unified schema.
- • Architected the code-printing pipeline → live unified API.
- • Led no-code page generation (Schema→API→Page) for consistent UX across types in real time.
- • Pre-mojoh ERP low-code proved the approach; mojoh removes those limits.
Madhu Krishna Murthy
Head of Delivery
Unfair Advantage
Drives faster, safer releases with low-code automation, governed playbooks, and tight product–engineering–customer alignment.
Proof Points
- • Built repeatable release frameworks standardising pilot→production across UI, schema, API.
- • Automated validation + cutover for zero-downtime deployments.
- • Scaled cadence; every release meets governance + adoption gates.
Heming Ni
Head of Application Engineering
Unfair Advantage
Built mojoh's unified API and no-code engine to design once, scale UI/UX everywhere — native pages for any knowledge type.
Proof Points
- • Implemented the unified API; every mote is addressable/composable via one interface.
- • Built the auto-page generator (config → native Blazor pages), no code required.
- • Eliminated redundant UI builds; consistent patterns; CI/CD on Azure/AWS.
Round & use of funds
Stage: Pre-seed
We're raising a focused round to turn early ERP programmes into a repeatable motion and deepen the mojoh graph and per-component helper model.
Use of funds:
- Product: expand and harden ERP templates and flows (starting with Oracle Retail and D365 Business Central), including migration, integration, data-quality and rollback tooling.
- Graph & helpers: deepen the knowledge graph and schema-aware UI components, so local helpers on any field can be more valuable as more domains are added.
- Go-to-market: land more design partners and SIs on ERP stacks like SAP, D365 F&O, NetSuite, Stibo and ServiceNow, and improve docs/onboarding so teams can build on mojoh with less hand-holding.
Details on round size and timing live in the deck — if this is your lane, request it or book a 20-minute intro.
Get in touch
If this resonates, we can go deeper in the deck.
General Inquiries
contact@mojoh.ioOffice
Level 1, 53 Walker StreetNorth Sydney, NSW 2060
Australia