NomadFlow
Your M365 tenant. A usable product.
NomadFlow turns a Microsoft 365 tenant into a product a team actually uses, with Dataverse as the data layer. One codebase ships two ways: a standalone Power Apps code app and a model-driven web resource, so it works whether the client licenses Power Apps or runs it as a web resource.
Not a video.The real app, live. No sign-up.
Deployed and running for a bank back office. The portal uses a real Postgres database, not static fixtures.
NomadFlow. Your M365 tenant, productised
By the numbers
- ships two ways
- 1 codebase
- as the data layer
- Dataverse
- reusable components and services
- 60+
- fewer data requests by default
- 95%
ships two ways
as the data layer
reusable components and services
fewer data requests by default
One codebase, two ways
Build it once, ship it however the tenant runs
The usual M365 build forks per surface and re-keys schema changes by hand. NomadFlow keeps one codebase behind a data seam and produces both targets.
| Dimension | The usual M365 build | NomadFlow |
|---|---|---|
| How it ships | Build a Power Apps app and a separate web build, then maintain both. | Two build targets from one codebase: a Power Apps code app and a model-driven web resource. |
| Schema changes | Edit tables in the UI and hand-fix forms; a field rename ripples through dozens of places. | Change one prefix line; the schema, forms, audit, and access regenerate across every surface. |
| Data requests | Pull a thousand rows and filter and sort in the browser. | Push select, filter, and sort to the server with paged reads, so there are far fewer requests. |
| Audit trail | Hand-rolled logging that misses UI-flow events. | Every create, update, and delete logged automatically, with human-readable field labels. |
| Role-based access | Security roles plus hand-coded visibility rules on each form. | Role gating at route, component, and action level, read from the tenant. |
Capabilities
What it does
- Dashboard
- Activity at a glance: entry totals, status breakdown, and monthly volume.
- Entries
- Track documentation entries and their review status, from list to detail to edit.
- Staff and contacts
- Team members with their roles, and the customer contacts they work with.
- Role-based access
- Sidebar and screens gate on the signed-in user's role, read from the tenant.
- Analytics and audit
- Reporting across entries and a full change history.
How it is built
One codebase, two ship targets, on your Microsoft 365
A single schema-driven React codebase produces both a Power Apps code app and a model-driven web resource, reading and writing your own Dataverse, wired into the Microsoft 365 you already pay for.
One codebase
Schema-driven, edit once
React and ViteOne UI codebase- Schema registryEntities defined once
- Repository adaptersMock, code-app, web API
Two ship targets
However the tenant runs
Power Apps code appA standalone URL- Model-driven web resourceRides an existing seat
Your Microsoft 365
Your own tenant
DataverseThe data layer
Power AutomateFlows and notifications
Microsoft GraphIdentity and M365 data
Governed
Read from the tenant
- Role-based accessRoute, screen, action
- Server-side pagingFilter and sort pushed down
- Audit trailEvery change logged
The public demo runs the mock adapter on representative data; the same codebase points at a live Dataverse in a client tenant.
The stack
The Microsoft platform you already own
Nothing new to license. NomadFlow builds on the Power Platform, Dataverse, and Microsoft 365 a client already pays for, behind one maintainable codebase.
- One codebase
- React 19
ViteOData - Power Platform and M365
- DataversePower AppsPower AutomateMicrosoft Graph
- Identity and access
Microsoft Entra IDRole-based accessAudit trail
Who it helps
A product the whole team can use
The same build serves the people doing the work, the people watching the queue, and the people who keep it running.
Your team
The people doing the work
- Enter and review documentation from list to detail to edit, inside the Microsoft 365 they already sign into.
- Filter and sort long lists with server-side paging, so the workspace stays fast as records grow.
- Each entry now carries its priority, review and approval dates, and customer detail, so nothing is lost between hand-offs.
Supervisors and leads
The people watching the queue
- Dashboards roll up entry totals, status breakdown, and monthly volume at a glance.
- A full change history shows who changed what and when, across every entry.
- Priority and review dates surface what is aging or waiting on a sign-off.
IT and admins
The people who keep it running
- One codebase ships two ways, a Power Apps code app and a model-driven web resource, so there is one build to maintain.
- Access reads from the tenant: the sidebar and screens gate on the signed-in role.
- Change a single prefix to rebrand the whole app; the schema regenerates forms, lists, and audit.
Architecture and security
Enterprise patterns, applied reliably
- Dual-target deployment.
- A code app for a standalone URL, or a single-file web resource that rides an existing model-driven seat. The client picks the licensing.
- Config-driven everything.
- A schema registry drives forms, audit, and access from one place. One prefix change rebrands the whole app.
- Transactional audit.
- Create, update, and delete writes log to an audit trail with before-and-after values and readable labels.
- Tenant identity and roles.
- Signed-in identity comes from Microsoft Entra; access gates on the tenant role at three levels.
- A data seam, not a rewrite.
- A Repository<T> seam (mock, code-apps, web-API) means the screens never change when the backend does.
Try it
What you can try
Five minutes, no sign-up required.
- 1Open the Credit Operations unit and browse the full recovery case portfolio, live from the database
- 2Open any case file, edit a field or add a debtor, and confirm the write persists on refresh
- 3Switch to the Payments unit and check the daily work-volume dashboard
- 4Use the unit switcher at the top of the chrome to move between PSU, LSV, CRO, and DCS
- 5Open Management in Credit Operations to edit choice fields, staff, and lookup tables
Under the hood
How it works.
Want software built around your business?
Tell us the goal in your own words. We reply with a 60-minute call, an honest yes-or-no on whether we are the right fit, and a one-page sketch of how it could work. No obligation.
- Replies within one working day, usually sooner. Trinidad business hours (UTC-4).
- Your details stay between us. See the privacy notice.