Automation for MSPs, without a key to your systems.
You need work built. You do not want one more outside team holding logins to your ticket system, your monitoring tool and every client you look after. So we work the other way round.
Most jobs
We hold no key at all
We build in our own test copies and hand you the finished files. You put in your own logins. Nothing of yours is open to us at any point.
Some jobs
One key, with an end date
Joining two of your tools means touching them. You make the login, you keep it, and it is switched off the day the work is signed off.
Never
Standing access to client tenants
We do not ask for a permanent login across the businesses you look after. Not at the start and not later. If a job needs that, we will say so and scope it another way.
What it costs. One fixed price per job, in writing, before anything starts. No monthly fee for a platform, because we do not sell one. You bill the work on at your own rate, and what you charge is your business, not ours.
We build it in our own copy, not in yours.
Most of the tools your work sits on hand out free test copies. Halo ships one. Microsoft gives out a full test tenant that renews. ConnectWise gives test instances to registered builders. We build there, against sample data you send us, and your live work is never in the room.
When it is finished you get five things, and the list does not change:
- The workflows themselves, as plain files you can open and read
- A short written guide: what each one does, and how it fails
- The list of logins the system needs, so you create them in your own accounts
- A test run you can watch, against your own copy, before it goes anywhere near live work
- Ninety days of fixes after it goes live, at no charge
You put it live yourself, with your own logins. If you would rather we did that part with you, we do it on a screen share while you watch. You make the login, and you can switch it off.
When a job does need a login, here is how we ask.
Some work cannot be done blind. Making your ticket system (your PSA) talk to another tool means touching that system. When that happens, four things are true every time.
-
A narrow login, never an admin account.
Halo and most modern tools let you switch on only the parts a job needs. We write down which parts, and why each one is needed, before you create anything.
-
Your account, your login, your control.
You make it. You hold it. You can look at it and you can end it in one click, at any hour, without asking us first.
-
A start date and an end date, agreed in writing.
The login is switched off on the day the work is signed off. If we need it longer, we ask you again and you decide again.
-
A record of what we did, where you can read it.
Every change is logged: who, what, when. It sits in your own system, not in a report we write about ourselves.
Your insurer asks whether outside firms hold access to your systems, and the answer has to be exact. This is written so you can answer it in one line.
What we build for MSPs.
The jobs that repeat, and the ones you have sold a client and now have to deliver.
-
Starting and ending a client’s staff
A new joiner set up the same way every time. A leaver closed off the same way. The steps are written down, and nothing is left to memory.
-
Paperwork nobody should still be typing
Quotes, invoices, forms and reports that arrive as files and get retyped into something else. Paperwork that gets retyped.
-
Systems for your clients, under your name
Tables, forms and approvals for the client whose work has outgrown a spreadsheet. Business systems we build.
-
Making two tools talk to each other
We join a system you use to one you do not. It stops rather than making a mess when the other side changes. Work that runs on its own.
-
Something that asks a person first
It reads what came in and works out what should happen. Then it waits for one of your people to say yes.
You own it, and you can take it anywhere.
What we build is plain files. You can open them, read them, copy them and move them to another server. The tool we build most of this on is open source, and you can run it yourself on your own machine.
If you stop working with us tomorrow, nothing stops running and nothing sits locked inside an account we control. There is no part of it that only we can open.
Ask the same question of anything else you are buying. Where do the workflows live, who can export them, and what happens to them the month you leave.
What we stay out of.
We build. That is the whole job, and keeping it narrow is what makes the rest of this page possible.
-
We do not answer for you
No phones, no help desk, no overnight watch room. Your clients hear from your people, which is how you want it.
-
We do not sit in your ticket queue
That is the point of us. The person who was going to build this keeps getting pulled onto client work. We are the team that cannot be pulled.
-
We do not resell anything
We take no fee from any software maker and we do not sit between you and a bill. You buy your own tools, in your own name, at your own price.
Who you are dealing with.
Noorflows is a registered company in the United States, with a team of certified developers. Our filings are public, and you can look us up before you speak to us.
Noorflows LLC
Registered in Wyoming, United States.
221 N Hogan Street, STE 414-65343, Jacksonville, FL 32202
Before any work starts we will tell you, in writing, who will be doing it and what they will be able to reach. How we handle your data.
The promise, with the conditions next to it.
-
A written list of checks, agreed before we start.
We write down what the finished thing has to get right, using your real cases. That list is the only test. If a check fails we keep fixing it at no extra cost.
-
A date, and a clock that pauses.
You get a date in writing once the list is agreed. The clock pauses while we are waiting on you, for sample data or a decision.
-
We come back on day 7, day 14 and day 30.
Named days. The first week is when real work behaves differently from samples. The thirtieth is when we find out whether your people are actually using it.
-
A full refund inside seven days if it misses the scope.
The written list above is the scope. If what we deliver does not do what that list says, email us within seven days of delivery and the payment comes back. That is the same clause in our terms, not a friendlier version of it for a sales page.
Questions we get asked.
-
Do you know our tools?
We work with the connections your tools publish, and we say plainly which ones we have built against before. We will not claim years inside a system we have not run.
-
Why would we not just build this ourselves?
Often you could. The tool is rarely the problem. The problem is that the person who was going to build it is on a client site, and six months later nothing has shipped.
-
Can you work under our name?
Yes. We are happy to be invisible. Everything we hand over is yours to present as your own work, and we will not name you anywhere without your written say-so.
-
What happens when it breaks at 2am?
We build it to stop rather than carry on wrongly, and to tell somebody it stopped. We also offer a monthly arrangement where that somebody is us.
-
How do we start small?
Send one process. We come back with what it takes and a fixed price. If it is not worth building, we will tell you that instead.
Not sure which of these fits how you work?
Write to us and describe the problem in your own words — no form, no call. We will tell you which one we would pick, what is good and bad about that choice, where it would be the wrong buy, and what it costs. If the honest answer is that you do not need any of it, we will say that instead.
Send us one process.
Tell us what it is, how often it runs, and which tools it touches. We come back with what it takes, a fixed price, and whether we need a login at all. We reply within one business day.