Web applications & client portals
Software built
around the work.
Bring requests, people and decisions into a useful web application.
NG Labs scopes and develops web apps, client portals and connected workflows. Start with the task people return to, then give it a clear path.
A request needs a decision.
One record. Clear roles. An agreed next step.
Customer adds a request
Required information arrives with the right record.
Draft → Ready for reviewReviewer checks the details
Questions stay attached to the work they concern.
In review → Needs a changeApprover records the decision
The current version and decision have an owner.
Ready → ApprovedAn example of a workflow to define together. It represents no client account, live integration or delivery result.
Choose the useful shape
A product with
a clear purpose.
Some tasks need an internal workspace. Others need a shared view with customers. We define the people, records and decisions before choosing the screens.
Web application development
A recurring operational task, a focused user journey and the information needed to complete it.
Client portal development
A shared place for requests, documents or approvals, with access shaped around the people involved.
Existing systems matter. Integrations are scoped around available access, source records, failure handling and an agreed owner; a familiar tool name alone is not an implementation plan.
Before the feature list
The missing part
is often a rule.
Who can change a request after approval? What happens when an update fails? A useful product brief makes those decisions visible.
Write a client portal brief- Task
- The action someone needs to complete, and what useful completion means.
- Record
- The item that carries the work: a request, file, booking or approval.
- Role
- Who may see it, change it and make the next decision.
- Exception
- The state that needs attention, and the person responsible for it.
From outline to handover
Make the first version
reviewable.
Agree the important journey and its boundaries. Review the product against those decisions, rather than treating a list of screens as proof that the work is complete.
Shape a bounded release
Map the current task, confirm the necessary access and separate the first useful version from later ideas. A prototype can resolve questions before implementation; it is not a production release.
Keep ownership clear
Agree source, accounts, data, deployment, testing and support responsibilities. Integration access, hosting costs and operational work belong in the scope, with a named decision maker.
Start with the work
What needs to
move forward?
Tell us who does the task, what happens today and where it gets stuck. We can start a scope conversation from that.
hello@northgrowthlab.com · We work remotely.
Integration planning
Decide recovery before you build.
Define unresolved states, repeat decisions and the evidence needed to close an exchange.
Before commissioning a portal
Test the task before buying the tool.
Compare a configured service with custom development using a workflow decision table and a small pilot.