Web application development
Your workflow,
one connected product
We design and build portals and operational platforms around your users, business rules and connected systems.
Rated 5 stars on Clutch.
Workflow design / User roles / Connected systems
Somerset West, Cape Town / Working globally
A few of the brands we’ve worked with
Who sees what
The right access for every role
A public website, authenticated portal and internal workflow can serve different users. We define the roles, access and integrations around your requirements.
Public website
Explain the organisation and give each audience a clear way in.
Public experience
Authenticated portal
Give each role access to the tasks and information it needs.
Role-based workspace
Internal workflow
Handle review, administration and agreed next steps behind the scenes.
Team operations
Selected work
OMNification / Product strategy, UX and application development
From campaign booking
to delivery evidence
We built an operations dashboard, a four-step booking journey and station-partner workspaces for Motherland OMNi. Campaign planning, delivery evidence, exceptions and reporting share one platform.
Design the handover.
Then build the product.
We establish who starts each task, what information they need, how it passes to the next person and what happens when there is an exception.
Those requirements define user roles, key journeys and the first release before we recommend a technical approach.
From a first release
to a product people use
You might need a new platform, a dedicated portal or a clearer experience in an existing product. The workflow and technical requirements set the scope.
01
Define the workflow
Map users, rules, information and exceptions. Identify the first release and the questions that need technical assessment.
Workflow maps / User roles and rules / First-release requirements
02
Prototype key journeys
Review tasks and interface states before the full build. Clarify what each role can see, change and complete.
Key journey prototypes / Interface states / Role-based experience design
03
Build and connect
Develop the functionality, permissions and integrations around the systems and data available to your team.
Application functionality / Agreed integrations / Permissions and data flows
04
Check and evolve
Test against agreed acceptance criteria. Plan release, support ownership and the order of future improvements.
Acceptance checks / Release plan / Support and development priorities
Karo Mining / Corporate website, authenticated portal and UX
A public website,
a separate authenticated portal
For Karo Mining, we linked public corporate information to dedicated portal routes for tender discovery, applications and administration. Suppliers and candidates have an environment suited to their tasks.
Working together
It starts with the people who know the work
Your team knows the work and business rules. We bring product design and software development, with clear review points along the way.
01
Map the workflow
Walk through the current workflow, users, systems and points of friction. Identify the business rules, exceptions and information the product must accommodate.
02
Plan the platform
Define the first release, integrations and acceptance criteria. Agree who makes decisions, supplies access and data, and reviews the product.
03
Build in stages
Prototype important journeys, build the functionality and review working stages with your team. Check how the roles and systems interact.
04
Launch and evolve
Review the release against the acceptance criteria. Confirm ownership, support and the order of future improvements as people start using the platform.
A release is one step
in the product’s life
We keep supporting the platform and building improvements after release, with responsibilities and priorities agreed with your team.
Before we
get started
A custom application makes sense when an important workflow depends on roles, business rules or connections your current tools don’t support well. We first check whether a new product, an integration or a simpler improvement fits the problem.
We assess the systems, data, access and interfaces available before confirming which integrations are feasible. The scope then defines each connection and who is responsible for it.
Yes. User roles, permissions and the information each person needs are part of the requirements work. We define the intended access model with your team and include checks for it in the test plan.
The examples on this page are web platforms and portals. If you need a native mobile app, bring your device, distribution and feature requirements, and we’ll assess the right approach and scope.
Web application timelines depend on your workflows, integrations, data, testing and the size of your first release. We set phases and review points once we’ve assessed those. A website timeline isn’t a reliable guide for a custom application.
It depends on the workflows, the integrations and the size of the first release. Every hour is scoped and quoted before work starts.
We talk through the workflow, users and systems involved, and tell you where we’d start. It takes 30 minutes.
Which workflow would you like to improve?
Walk us through the people, systems and handovers involved. We’ll discuss where an application or integration could help.
A 30-minute call. No brief needed.