Case study · inward-facing
The same machinery, pointed at your own team
The same company also ships three roles to its own staff: one for sales, one for the specialists who answer technical questions, one for marketing. Built the same way, installed the same way, in the same app. Three things change, and every one of them follows from the audience being inside the company rather than outside it.
Anonymised. No pipeline structure, performance data, competitor information, staff details or system names appear on this page.
The three things that change
One
It runs without being asked.
The customer bundle has eight workflows and nearly all of them wait for a person. The internal one has roughly three times as many, and most run on a schedule or poll a mailbox: a morning pulse, a weekly digest, a check for anything that went quiet. The boards read what those runs produced, which is why opening one is instant and does not hammer the systems behind it.
Two
The credentials are the organisation’s, and nobody configures anything.
Where the customer bundle asks people to bring their own sign-in, the internal one ships the company’s, sealed. A new hire installs the app, signs in, and their role is connected to the systems it needs on the first morning. That is only defensible because of how it is delivered: the server fetches the private copy itself, the access key never reaches a laptop, and removing someone from the group stops their access within about fifteen minutes.
Three
Nobody gets a role by default.
The customer bundle switches its main role on for you, because there is only one thing you came for. The internal one switches none of them on, because a person in sales is not in marketing and forcing them into the wrong role on launch is a worse first impression than an empty one. Roles are namespaced too, so somebody who is both a member of staff and a user of the product can hold both bundles at once without them colliding.
The two side by side
| Customer-facing | Internal | |
|---|---|---|
| Who it is for | Customers, outside the company | Staff, inside it |
| Where the page lives | Indexed, linked, public | Behind sign-in, noindex, unlinked |
| Who fetches the content | The person, or the app | The server, and only for an entitled member |
| Connector credentials | Sealed and scoped per person, or bring your own | Sealed once for the organisation, zero setup |
| Workflows | Mostly started by a person | Mostly on a schedule or polling a mailbox |
| Dashboards | Mostly fixed reference tables | Bound to scheduled runs, showing live numbers |
| Sample data | None | Bundled, in the real export format |
| Role switching | One role is switched on for you | You choose, because not every role is yours |
The pattern worth stealing
A scheduled workflow with no AI in it computes the numbers once, early, and writes them down. Every board widget reads that. Nobody waits on a live query, the figures on two screens agree because they came from the same run, and the systems behind them are touched on a schedule you chose rather than on every page view.
It is the least glamorous idea in either bundle and the one that makes the rest usable.
Want this for your team?
Talk to us