Map how work actually happens.
Oroko is process mapping and documentation software built for process clarity. Map the work, capture the operational context, understand what needs to change, design the future state and generate the procedure from one structured process record.
Oroko
Real Oroko canvas — the Customer Onboarding map, current state.
Built for
The process data is the product. The canvas is just the way you see it — change a step once, and the procedure, the analysis and the sign-off all change with it.
Most process tools make you keep the diagram, SOP, analysis and improvement plan in sync by hand. In Oroko they stay connected because they are views of the same structured process.
More than a diagram.
Capture the process once, then use the same structured information for analysis, future-state design, procedures, governance and improvement planning.
Structured mapping
Map activities, decisions, owners, roles, systems, inputs and outputs without wrestling with a blank whiteboard.
Contextual analysis
Capture pain points, requirements and open questions against the exact step they belong to, then move straight back to the map.
Current and future state
Model today and tomorrow separately, then compare the change without losing the context behind either state.
Procedure generation
Turn the map, including subprocesses, into an operating guide without rewriting the same process in another document.
Governance & sharing
Review, approve, version and share the right process view while keeping workspace editing and public access separate.
Improvement roadmap
Promote meaningful issues and proposed changes into a workspace roadmap so teams can see what is improving and when.
Reads like a document your team will actually use.
Every procedure is generated straight from the map — numbered steps, owners and flagged issues, formatted to read like a real operating document instead of an exported diagram.
- Stays connected to the map — edit a step, the document updates itself
- Flagged issues appear as inline highlights, not buried in a separate report
- Click straight through to the exact step on the canvas, and back
Actual interaction in Oroko — Library → Map → Procedure → Analysis.
Simple first. Powerful in layers.
A user should be able to map a process in minutes. When the work demands more, Oroko reveals analysis, solution, future-state, roadmap and governance depth without making the core experience heavy.
One structured process. Different jobs.
Use the same foundation whether you are discovering how work happens, redesigning it, documenting it or helping a client understand it.
Capture how work really happens during interviews, workshops and operational reviews.
Connect issues to their source step, propose the change, design the Future State and prioritise improvements.
Generate the operating procedure, route review and approval, keep history and share the right version.
Use one structured record across discovery, client documentation, redesign and handover instead of rebuilding the same process repeatedly.
Start small. Add capacity when the work grows.
Oroko is priced around the scale of the workspace, not around locking core process features behind complicated tiers. The same structured process model remains available as teams grow.
These are our working launch plans while we validate real usage during beta. Process, seat, storage and API/MCP allocations will be finalised from observed usage before paid launch.
Launch pricing previewNeed more processes or seats? Add capacity as you grow. Final add-on allocations and API/MCP allowances are being validated ahead of paid launch.
Start free →Built to make work easier to understand
Oroko began with a simple idea rooted in Korokoro, the Urhobo word behind its original concept: see clearly.
Too many important processes live across conversations, documents, spreadsheets and disconnected diagrams. Teams may know that work is getting done, but not always how it moves, who owns each step or where the friction sits.
Oroko is being built to change that.
It gives teams one structured place to map how work happens, capture the operational detail behind each step and turn that understanding into analysis, future states, procedures, governance and improvement priorities. The goal is not to create another complicated diagramming or project-management tool. It is to help people move from scattered information to a clear, shared understanding of the work.
Built in Nigeria. Accessible by design. Globally usable.
Why we're building it
We believe process tools should support the conversation rather than slow it down. A user should be able to map a process during a workshop, add the right context as they learn more and produce useful documentation without rebuilding the same information in several different tools.
That's why Oroko is designed to be:
- Simple enough to use from the first step
- Structured enough for professional work
- Visual without becoming an infinite whiteboard
- Detailed without making the canvas feel crowded
- Useful across discovery, operations, redesign and governance
Build the process once. Keep the understanding connected.
Start with a real process and see how the map, analysis, future state, procedure and governance stay together.