Client intake into SharePoint
A new client's details and documents arrive once. They land in the right SharePoint folder and your practice system, and the next person gets told. Nobody retypes the engagement form.
The Microsoft 365 Workflow Fix · $3,500 fixed
Client intake, approvals and new-hire setup, built inside your own Microsoft 365.
Pick the handoff your practice still does by hand. We build it inside your own Microsoft 365 and connect it to the system you already run. Then we hand it over documented, under your admin. $3,500 fixed. No retainer, and you keep the keys.
Written reply within one business day. No call required.
$3,500 fixed for one workflow · about 10 business days once access arrives · licenses separate
Fails the acceptance test we agree in writing? One free in-scope fix, up to 2 hours, then a retest. If it fails again, you choose 10% of the fee back as a partial refund or credit, up to $350.
Rather talk it through? Call us at (770) 649-3525.
- Built in your own Microsoft 365, under accounts you own
- The acceptance test is in writing before you commit
- Switch it off and the manual way still works
- The written reply is free, and no call is needed
What $3,500 buys inside your Microsoft 365
One workflow built inside your own Microsoft 365: client intake, an approval, staff onboarding or offboarding, or a document someone re-keys into another system. We check the native tools first, build only what's missing, route anything that fails to a named person on your team, and hand it over documented, in your tenant, under your admin. Switch it off and your manual process still works. Nothing is deleted, nothing is moved, and you can disable it yourself in your own portal.
$3,500 fixed, about 10 business days once access arrives. Software and licenses sit outside the price.
If it's clearly smaller or bigger than usual, the written quote lands between $3,000 and $4,500, before you commit. Licenses and premium connectors sit outside the price, and nothing gets bought without your OK. Changes after sign-off, and anything outside the scope, run $80 to $100 an hour, quoted first.
Here's the arithmetic we'll run with your numbers. Eight new clients a week at 20 minutes each is about 2.7 hours a week, close to 140 hours a year. That's an example, and it measures time, not money saved. Below about two hours a week, we'll usually point you to the walkthrough or a small hourly fix instead.
Fixing onboarding and offboarding together? Book them in one scope round and the pair is $5,600 instead of $7,000, with the same HR system or directory and one owner on your side. They run back to back, about 15 to 18 business days in all, each with its own acceptance test and its own remedy, worked out on the discounted fee. Drop one before sign-off and the other reverts to $3,500. Switch either one off and that manual process still works.
The handoffs we build in Microsoft 365
Approvals that don't sit in an inbox
Requests go to the right approver in Teams or Outlook, with a reminder, a backup approver for the week someone's out, and a record of who said yes.
Staff onboarding and offboarding in Entra ID
A new hire's account, groups and licenses are ready on day one. A leaver's access comes out the day they go, and anyone who needs to can see that it did.
The document someone re-keys
An invoice, a timesheet or an intake form that gets typed from one system into another moves once, with a person checking it where it matters.
How a Microsoft 365 workflow gets built
- We time the handoff as it runs today, then write the acceptance test. It covers the normal cases and the ugly ones: a duplicate request, an approver who's out, a system that times out halfway through. The finish line exists before any building does.
- Native tools come first. Microsoft Lists, Forms, Teams approvals or your practice software may already cover half the job, and switching that on beats paying for something new. If a setting fixes it, you'll hear that from us, even when it means there's no project.
- Then we build only what's missing, usually a Power Automate flow running off a SharePoint list or a form, with the Entra ID account, group and license steps done through Microsoft Graph or PowerShell where a flow can't reach. It connects to the practice-management, CRM or accounting system you already run.
- Anything it can't handle cleanly goes to a named person on your team, with an audit trail of every change it made. A failure lands with a person instead of a log nobody reads.
- At handover you get the runbook: what it does, which account owns each connection, how to switch it off, and how to run the manual process if you ever need to. Our access comes out the same day.
We check licenses before we quote. Microsoft's built-in Lifecycle Workflows need Entra ID Governance, which Business Premium doesn't include, so we build on what you already pay for wherever we can, and name anything that costs extra before you commit.
For whoever holds global admin
The first thing we'll ask: "Who holds global admin on your Microsoft 365 tenant today: someone in-house, or your IT provider?"
Whoever it is, here's what they're agreeing to. We work under a named account with only the roles the build needs, time-boxed, with your change process in front of it. The access list arrives in writing before anything is touched. We never ask for shared global admin credentials, and at handover our account comes out. The flows, their connections and the account they run under are documented and owned in your tenant, so removing our access doesn't break anything.
If an IT provider runs your tenant, we ask them for scoped, time-boxed access under their change control, and the runbook goes to them as well as to you. If they'd rather not grant it, we'll tell you plainly and stop there.
Built and run by us
Our founder has built onboarding and offboarding automation on n8n and Make, and an access review that checks Active Directory changes against Jira tickets. Our own Windows, Linux and VMware lab runs single sign-on and TLS we manage ourselves. We run monthly restore tests through the Cohesity API, and we built and still run Compass, a finance app at privatecompass.app, plus this website. None of it is client work. What it shows is the plumbing your handoff needs: accounts, groups, approvals, and a record of who changed what.
Credentials held at Chrysis: Microsoft Azure Fundamentals, Microsoft MTA Database Fundamentals (held; the program was retired in 2022), VMware VCP-DCV and VCTA, Cohesity Knowledge Expert, Sophos Certified Firewall Engineer.
Chrysis Networks is a Microsoft Partner and a Pax8 Partner. Both are company memberships, with no tier or specialization attached, and we won't dress them up as one.
Questions about Microsoft 365 workflows
How much does it cost to automate a handoff in Microsoft 365?
$3,500 fixed for one workflow in your own Microsoft 365, quoted at $3,000 to $4,500 if it's clearly smaller or bigger. Licenses are extra; no retainer. Switch it off and your manual process still works. Miss the agreed acceptance test and we fix it free (up to 2 hours), then retest. Still failing? 10% back, up to $350.
What does the Workflow Fix include?
One workflow: client intake, an approval, staff onboarding or offboarding, or a document handoff. We check the native tools first, build only what's missing, route failures to a named person and hand it over documented, in your tenant, under your admin. Switch it off and your manual process still works, because nothing is deleted or moved.
Who owns the automation after you hand it over?
You do. It's built in your Microsoft 365 tenant, under accounts you own, and documented in a runbook your team keeps: what it does, which account owns each connection, and how to switch it off. At handover our access comes out, so we hold no credentials to your tenant afterwards.
How long does it take?
About 10 business days once access, a few sample cases and an owner on your side are in place. The clock starts when access arrives, and waiting on a vendor or on your team pauses it. Onboarding and offboarding booked together run about 15 to 18 business days.
What happens if it breaks, or we want to switch it off?
A stalled approval, a failed connector or a duplicate goes to a named person. Switch it off and your manual process still works: nothing is deleted, and you can disable it in your own portal. If it misses the test we agreed, we fix it free (up to 2 hours) and retest. Still failing? 10% back, up to $350.
What access do you need to our Microsoft 365?
A named account with only the roles the build needs, time-boxed and removed at handover. You get the access list in writing before anything is touched, and your change process stays in front of it. We never ask for shared global admin credentials.
We have an IT provider. Can you still do this?
Yes. We ask your IT provider for scoped, time-boxed access under their change control, and the runbook goes to them as well as to you. If they'd rather not grant access, we'll tell you plainly and stop there.
Who is this for, and who isn't it for?
Operations leaders at accounting, legal, consulting and engineering practices of roughly 20 to 100 people on Microsoft 365, with one handoff done by hand often enough to matter. It isn't for a whole-tenant overhaul, an hourly IT seat, compliance attestations or practices on Google Workspace.
What is the $350 tenant walkthrough?
A paid look inside your Microsoft 365 when it's genuinely unclear what it can do for your handoff: up to five hours, including written findings on what's native, what's missing and what we'd build. The $350 is credited in full against the Workflow Fix. A clear job skips it and gets a fixed-price quote straight away.
Can our existing Microsoft 365 do this without a custom build?
Sometimes, and we check that first: Lists, Forms, Teams approvals or your practice software may already cover it. Business Basic, Standard and Premium include Power Automate with standard connectors. Premium connectors cost extra, and Lifecycle Workflows need Entra ID Governance, which Business Premium doesn't include. Anything license-gated is named, with its cost, before you commit.
Describe the handoff
Tell us what gets done by hand today and which software it touches. Within one business day you'll get a written reply from the firm that would build it: whether it fits, what a fixed-price scope would cover, and the first thing we'd check. No call needed, unless you'd rather talk.
Three quick answers. We'll say if it fits.
Not ready to write up the whole handoff? Tell us three things and we'll reply in writing within one business day, saying plainly whether it's a $3,500 Workflow Fix.
Not a Microsoft 365 job?
Same firm, same written scope and acceptance test. Different job.
Automation and integrations
The Workflow Fix, outside Microsoft 365
One handoff on n8n or Make, or a repair to one that broke. $3,500 fixed, and your manual process still works if you switch it off.
See Automation & IntegrationsPractical AI
Reviewed AI, $4,500
AI does the first read on one kind of document. Anything it's unsure of goes to a person for approval. Model usage and software fees are separate.
See Practical AIInfrastructure
The Infrastructure Fix, $5,500
One defined change, like Conditional Access across your tenant or retiring a server that's out of support, with the rollback tested before anything moves.
See InfrastructureWebsites and hosting
The Website Build, $3,500
Up to five pages you own outright, with the contact form tested before launch.
See the Website Build