Internal app platform
A safe place for your staff to build and launch their own tools with AI.
With AI, your staff can build a working tool in an afternoon. What they can't do is make it safe. I build a platform in your own cloud account that handles sign-in, access, data and passwords for every tool, so they only build the tool.
In your own cloud account · your company sign-in · a fixed price in writing before I start
What every tool gets
- Sign-in through your company accounts, before anyone reaches the tool
- Access set by IT, from the staff directory it already manages
- Its own private database, with no password to leak
- Safe storage for the passwords and keys it needs
- Its own web address, and jobs that run on a schedule
- A private preview, so a change is checked before staff see it
Staff don't set any of this up, and they can't leave it out. It comes with the platform, the same for every tool.
What you get
- The platform, built in your own cloud account and yours to keep
- A starter tool your staff copy to begin a new one
- Your first tool live on it, so you see it work from start to finish
- Plain guides for the people building tools and for IT
- Every design decision written down, with the reason for it
- Me looking after it month to month, or a hand-over to your team
Built on what you already use
You don't move to a new cloud or teach staff a new sign-in. I set the platform up on the cloud and the sign-in your company already runs.
The whole setup is scripted and documented, so your team can rebuild it or change it without me.
- Your cloud
- Microsoft Azure, Amazon Web Services or Google Cloud. I build the platform in your account, so no new vendor holds your data.
- Your sign-in
- Microsoft Entra, Google Workspace or whichever company sign-in you already run. Staff use the accounts they have, and once IT closes a leaver's account they can't sign in to any tool.
- Your AI
- Staff build with the AI assistant you've approved. Nothing in the platform depends on which one.
Who does what
Security doesn't depend on the person building the tool.
Staff build the tool
A builder makes their tool with AI and adds a short file saying who can use it and what it needs. Hosting, sign-in and the database are set up for them. They release their own changes once the automated checks pass, without waiting on an engineer.
IT decides who gets in
Access comes from the staff directory IT already manages. Each tool opens only for the people and groups assigned to it.
The platform keeps it safe
Sign-in happens before a request reaches a tool, and tools contain no login code. A mistake in one tool can't make it public or open up another tool's data.
How it goes
From first call to your first tool
01
Call
30 minutes on what your staff want to build, which cloud and sign-in you run, and what data the tools will touch. Tools that hold patient or student records need extra safeguards, and I scope those up front.
02
Written proposal
Scope and a fixed price in plain language, before any work starts.
03
Build
I build the platform in your accounts and put a first tool on it, so you see it working with your own sign-in.
04
Hand-over or stay on
Your builders and IT get their guides, and your team runs it from there. Or I keep looking after it.
Where it's in use
A health-sector company wanted its own staff building internal tools, including ones that hold confidential business data. The platform was live the day after the request, with its first tool open to every employee, and IT decides who sees each one.
Want your staff building their own tools, safely?
Tell me what your staff want to build and which cloud and sign-in you run, then pick a time to talk it through. You'll get a fixed price in writing before anything starts.