Service 06
Custom Operational Apps on SharePoint & Microsoft 365
TechRam builds the operational apps your process actually needs on SharePoint and the Power Platform — registers, request routing, approvals and dashboards — on the Microsoft 365 licences you already hold. Each one is scoped at a fixed price, built and tested with the people who'll use it, then handed over.
- 2–16 weeks
Who it's for
Operations running on spreadsheets and inboxes for things that should be registers with owners, states and dates.
What we do
- Registers and trackers as real systems, not shared files
- Approvals and requests routed on rules rather than memory
- Integration so data is entered once
- Reporting off the register, for the people accountable for it
How it works
Step 1
Workshop the process as it actually runs
Step 2
Fixed scope and fixed price, agreed in writing
Step 3
Build, test with the people who will use it, document it
Step 4
Hand over, then improve on a cycle if you want us to
The problem it answers
The incident register is a spreadsheet. The asset list is a different spreadsheet. Renewals live in somebody’s calendar, and approvals happen in an email thread that ends when the person approving goes on leave.
None of these are bad decisions. Each one was the fastest thing available at the time. The cost only shows up later, when nobody can say what the current state is without asking three people.
What changes
The same processes become real systems: owners, states, reminders and an audit trail, built on the Microsoft licences you already pay for. The record is written as the work happens rather than reconstructed afterwards, which is also the only way an assistant can answer a question about work in progress.
Proof: Achieve Australia
Achieve Australia ran thirty onboarding and offboarding events a month by hand, across five systems with no single record of what happened. TechRam built one pipeline that starts from a single request and provisions accounts, licences, groups and devices — recovering 120 hours a month and $126K a year.
$126K
recovered a year
120 hrs
saved every month across the onboarding lifecycle
Built under this service
Online Claims Intake
One online claim form that files itself, instead of paper scanned, emailed and re-keyed.
Read the entry → — Online Claims IntakeHazard Management
Report, triage, close and report on hazards without a spreadsheet.
Read the entry → — Hazard ManagementMarketing Request Automation
Marketing and collateral requests raised once, routed on type, tracked to delivery.
Read the entry → — Marketing Request AutomationOKR & Objectives Tracker
Objectives, owners and progress in one place the executive actually opens.
Read the entry → — OKR & Objectives TrackerQuick Claim Submission
Support workers submit a claim in under a minute instead of a form and three emails.
Read the entry → — Quick Claim SubmissionWorker Onboarding & Offboarding Pipeline
Starter to system access in one pass, with an audit trail at the other end.
Read the entry → — Worker Onboarding & Offboarding Pipeline
Related reading
How do you build a better form over a SharePoint list?
Read it → — A better form over a SharePoint listHow do you prove your staff have read a policy?
Read it → — Proving staff have read a policyHow do you show a SharePoint list as a Gantt chart?
Read it → — A SharePoint list as a Gantt chartShould we buy another platform or build it in Microsoft 365?
Read it → — Buy a platform or build in Microsoft 365?How do you work out what a manual process actually costs?
Read it → — How do you work out what a manual process actually costs?
Start here for free
SharePoint Forms
Deploys in under 30 min
Deploy it in your own tenant → — SharePoint Forms
What this does for your AI
An app writes the record as the work happens, which is the only way an assistant can answer about work in progress.
Common questions
01. How is a custom operational app different from what our MSP already does?
An MSP supports software somebody else wrote. This builds the thing that doesn't exist yet, which is why it's scoped against your process rather than against a product.
02. Why not buy something off the shelf?
Often you should, and we'll say so. Buy when the process is standard. Build when the product would need configuring into something it wasn't designed to be, which is where the adoption failures come from.
03. Can we build the first app for one department rather than the whole organisation?
Usually yes, and it's often the better way in. One department that works is a more persuasive business case internally than a plan covering all of them, and it gives us a real cost to scope the rest against.
04. What does a custom operational app cost?
Fixed scope, quoted in writing before work starts, and the number doesn't move because the work turned out harder than we expected. We don't publish a range, because the scope is what sets it and a range without a scope is a guess you would have to unlearn.
05. Do we need to buy anything new to run a custom app?
Almost never. We start with what is already in your Microsoft 365 licensing, and we don't resell licences or earn a margin on them. Where something genuinely isn't covered we'll say so before you commit, not after.
06. What happens when the app is finished?
You own it: the systems, the documentation, and the ability to maintain them without us. Run & Improve exists if you would rather we kept it current, and it's monthly with no lock-in.