Canonical: [https://chrysisnetworks.com/services/it-automation-solutions]() Custom software, automation and integrations # Approved work nobody invoiced. A lead nobody owns. The gap between your systems is costing you. Your field, practice, CRM and accounting software each do one job. The work falls through between them. We build the missing piece: a custom tool, an integration, or a check that alerts a named person when a step stalls. Fixed price, quoted in writing once we've seen the handoff. Reply within one business day, no call. [Describe the handoff]() [Not ready to describe it? Just check the fit.]() Rather talk it through? Call us at [(770) 649-3525](). ![Two stone blocks joined by three gold cables]() ## Tell us which step keeps getting missed. We'll answer in writing. We've built onboarding and offboarding automation and an access review before, and whoever scopes yours builds it. The reply says whether it fits and what a fixed-price scope would cover. When it's genuinely unclear your systems can do the job, we'll say so and suggest a $350 walkthrough first. That $350 comes off the project price if you go ahead. What we've built and run ourselves Our founder has built onboarding and offboarding automations on n8n and Make. We run our own n8n server, so the platform under your workflow is one we operate ourselves. We also wrote [restore-validation tooling]() and shipped [Compass](), an app we built and still run. Microsoft Partner · Pax8 Partner · VMware VCP-DCV and VCTA - The written reply is free, and no call is needed - The acceptance test is in writing before you commit - Built and run by us: see the [restore-testing build log]() - We reply within one business day Also from Chrysis: [Practical AI]() · [Infrastructure]() · [Website Build]() ## Where the gap usually is Between the field and the office. A crew does extra work, the ticket gets signed, and then it sits in a truck or an inbox until nobody can price it. Or Jobber says a payment came in and QuickBooks never hears about it. **Automated invoicing.** Extra work your client signed for that never makes it onto an invoice. We connect the field or project software to QuickBooks, so a signed ticket or change order becomes a draft invoice line, and a named person approves it before it bills. Between the CRM and the people who deliver. A lead fills in the form and nobody's name is on it. A deal is marked won and the job never gets opened. **Automated CRM management.** A new enquiry nobody calls back hires whoever answered first. We set up or repair your CRM so every enquiry lands with a named owner and a follow-up date, and a deal marked won opens the job. **Automated ad campaigns.** You paid for the click, and nobody called the lead back. Whoever runs your ads keeps running them. We build what happens after the click: each enquiry routed to an owner, tracking tested until it fires and a weekly report of spend against enquiries. Budget changes wait for your approval. Between a request and a decision. Approvals live in email threads, and three months later nobody can find who said yes. Between a hire and a leaver. HR approves a new starter and someone builds the accounts by hand from a long checklist. When someone leaves, ask who shut off every account and you'll get three different answers. And sometimes no product covers it at all. That's when we write a small internal app or a scheduled job, built to be checked and owned by your team. It's for the person who can point at one of these and say: that one. Fix that. ## Custom software, when nothing off the shelf fits Most of what we build is custom, but it's small on purpose. We'd rather write one internal tool your team uses every day than sell you a platform you have to move into. We check the native features first: your field software, CRM or Microsoft 365 may already do half the job, and switching that on beats paying for something new. Then we build only what's missing, with an audit trail your team can read and failures sent to a named person instead of a log nobody opens. Bigger custom applications are quoted separately, in writing, before you commit. ### Also built here - Repairs to CRM, form and accounting workflows that stopped passing the right data - Internal web apps and scheduled jobs for problems no product covers - Restore testing that boots the backup and checks it from the inside, with a [published build log]() ## API integrations, so nobody retypes the same record twice Every record someone copies from one system into another can go in wrong, or not at all. A signed change order sits in the field app and never reaches QuickBooks. A web inquiry never becomes a matter in Clio, so nobody calls back. We connect the two through their APIs, once we've checked that no connector you already pay for does the job. Anything the integration can't place cleanly goes to a named person, and anything that bills waits for their approval. Awkward older systems are often workable. We check before quoting. For a worked example, see our [restore-testing pipeline](), which runs entirely against the Cohesity REST API. You get the documentation at handover, and our access comes out. ## 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 fits a fixed-price fix. ## How it works ![Three desk trays turning loose papers into sorted cards, linked by a gold line]() 1. We start by timing the process as it runs today and agreeing the target. Then the acceptance test gets written. It covers the normal cases and the ugly ones, like a duplicate request or a system that times out halfway through. So the finish line exists before any building does. 2. Native features come first. Your HR platform or directory may already handle half the job, and switching that on beats paying for something new. 3. Then we build the rest so it can be checked. Every change it makes lands in an audit trail your team can read. Anything it can't handle cleanly lands with a named person on your team instead of failing quietly, and your team gets a manual fallback for the day something upstream is down. ## On Microsoft 365: Power Automate, SharePoint and Entra ID, in your own tenant **Automated onboarding/offboarding.** A login from someone who left in the spring still works. It's the clearest case for building on Microsoft 365: accounts ready on day one and access closed the day someone leaves, with a named person approving every change. On Microsoft 365, it's the same Workflow Fix, built where your admins already work. That's usually a Power Automate flow running off a SharePoint list or a form, with the Entra ID account, group and license steps handled through Microsoft Graph or PowerShell where a flow can't reach. 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. Everything stays in your tenant, under accounts you own. At handover our access comes out and a runbook stays with your team. Enrolling laptops in Intune is a separate job, scoped on its own under Infrastructure. Switch it off and your manual process still works, because nothing is deleted or moved. Already on Microsoft 365? See [Microsoft 365 workflows](). ## On Google Workspace: n8n or Make, in accounts you own Running Google Workspace instead? The misses look the same: an inquiry sitting in a shared Gmail inbox with nobody's name on it, or a leaver whose account still opens. We build the same Workflow Fix with n8n or Make, after checking what Workspace and your other software already do on their own. It runs in accounts you own. Anything it can't handle goes to a named person, and the manual way keeps working. Same fixed price, same acceptance test. Here's the kind of target we might set: a case that takes 45 minutes by hand gets done in under 10. At 20 cases a month, that's over 11 hours of your team's time back. It's an example. Your real numbers come from timing your process. ## If it misses the test Done means it passes the acceptance test agreed at the start, so nobody argues later about whether it works. Miss it, and we fix it free, up to 2 hours inside the original scope, then run the test again. Still failing? You get 10% of the fee back as a partial refund or credit, up to $350, your choice. We'd rather put a number on it than promise something vague. Not sure your systems can do it at all? Sometimes we won't be either, and we'll say so. Then we'd suggest a $350 walkthrough first, and that $350 comes off the project price if you go ahead. A clear scope skips it. ## Who builds it Chrysis Networks is a custom software and automation firm led by Tyler Fameli, delivering remotely anywhere in the US. Onboarding and offboarding automation isn't new to us, and neither is checking records against tickets. Your systems will differ. The problem won't. We've also built an [access review]() that checks Active Directory changes against Jira tickets. Two things you can check today: the [published build log]() for our restore-testing pipeline, and Compass at [privatecompass.app](), an application built and run by Chrysis Networks. **Credentials held at Chrysis** Microsoft Partner · Pax8 Partner · VMware VCP-DCV and VCTA · Cohesity Knowledge Expert · Sophos Certified Firewall Engineer · Microsoft Azure Fundamentals ## What it costs Automation sounds expensive when it means automating everything. Ours starts smaller: we find the step that slips most, or costs most when it does, and fix that one at a fixed price, with the finish line written down before anything gets built. The Workflow Fix is $3,500 fixed for one handoff, your pick: field to office, CRM to delivery, an approval, onboarding, offboarding, or one place where data moves between systems. Need both onboarding and offboarding? Book them together and the pair is $5,600 instead of $7,000, 20% off. They're separate workflows, each quoted in writing before you commit: $3,500, or $3,000 to $4,500 if it's clearly smaller or bigger than usual. The pair price needs one scope round, 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. Drop one before sign-off and the other reverts to $3,500. Software and licenses 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. About 10 business days once access, inputs and an owner on your side are in place. Waiting on your team or a vendor pauses the clock. Whatever we build, your manual process still works if you switch it off: nothing is deleted, nothing is moved, and you can disable it yourself. 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. [Describe the handoff]() ## Asked and answered ### Can Chrysis build custom software for a small business, or only automations? Chrysis builds both: small internal web apps and scheduled jobs where no product covers the problem, and automations or integrations between systems a firm already runs, such as a field app, a CRM and QuickBooks. A single handoff is the $3,500 Workflow Fix; a larger custom application is scoped and quoted in writing before work starts. ### How much does it cost to automate employee onboarding and offboarding for a 50-person company? Chrysis Networks charges $3,500 fixed per workflow, delivered in about 10 business days once access arrives, and quotes $3,000 to $4,500 in writing when a job is clearly smaller or bigger. Booked together in one scope round, onboarding and offboarding cost $5,600 instead of $7,000 when both use the same HR system or directory and one owner on your side, running back to back over about 15 to 18 business days with an acceptance test each. Software and licenses are priced separately, and dropping one workflow before sign-off returns the other to $3,500. ### Should a small business use Power Automate, n8n, Make or Zapier for workflow automation? The right platform is usually the one a business already runs. Chrysis builds in Power Automate inside your own tenant on Microsoft 365 and on n8n or Make elsewhere, and Zapier is fine when your team already uses it. Native features come first either way, since a setting your HR platform or directory already includes beats paying for a new tool. ### Can Chrysis automate handoffs for a firm that runs Google Workspace instead of Microsoft 365? Yes. Firms on Google Workspace are in scope, and the Workflow Fix works the same way: Chrysis checks what Workspace and the firm's other software already do natively, then builds the missing piece with n8n or Make at the same $3,500 fixed price. The workflow runs in accounts the firm owns, sends anything it can't handle cleanly to a named person, and leaves the manual process intact. ### Can someone stop us retyping data between our CRM and accounting software, or fix the integration that used to do it? A customer record retyped from a CRM into accounting software, or a connection that stopped passing the right data after an update, is the kind of single handoff the $3,500 Workflow Fix covers. How well two systems connect depends on each one's API or connector and the way it handles sign-in, so Chrysis checks that before quoting. When feasibility is genuinely unclear, Chrysis suggests a $350 walkthrough first, credited to the project if you go ahead. ### Can Chrysis connect two of our systems through their APIs, even if one is old or has no ready-made connector? Usually, if each system offers an API, a supported connector or a dependable export. Chrysis first checks whether a native integration or a connector you already pay for does the job, then confirms each API's access and sign-in method before quoting, because that decides what the connection can do. A single connection is scoped as the $3,500 Workflow Fix, and records it can't place cleanly go to a named person on your team. When a system offers no usable route, Chrysis says so in writing instead of quoting a build. ### Is workflow automation worth the cost for a small company that only hires a few people a year? Low-volume onboarding often doesn't justify a build, and Chrysis will tell you so. Under about two staff hours a week, a native setting or a bounded hourly fix at $80 to $100 an hour usually makes more sense than the $3,500 Workflow Fix, which fits handoffs done by hand every week, like a 40-minute account setup repeated 15 times a month. ### What happens to our process if an automated workflow breaks or a connected system goes down? Anything a Chrysis workflow can't handle cleanly, such as a missing field or a system that times out halfway, lands with a named person on your team, and every change it makes is recorded in an audit trail anyone on your side can read. Your manual process stays available the whole time because nothing is deleted or moved, and you can switch the workflow off yourself. ### What if the automation doesn't pass the acceptance test we agreed? Chrysis writes the acceptance test before building anything, covering normal cases and ugly ones like a duplicate request or an approver who's out. A workflow that misses the agreed test gets one free fix of up to 2 hours inside the original scope and a retest, and if the retest fails you choose 10% of the fee back as a partial refund or credit, up to $350. ### How do contractors stop material requests getting ordered twice? One record per material request, with the job, an owner and an approval before anyone places the order, is what stops contractors buying the same materials twice: a second request for the same material on the same job gets flagged instead of bought. Chrysis first checks whether the purchasing features in your field or accounting software already do this, since switching on a setting beats paying for a build, and otherwise builds the request-and-approval step as a $3,500 fixed Workflow Fix. The crew keeps the app it already uses. ### How can a tax office or law firm stop chasing missing client documents by hand before a deadline? A tax office or law firm stops the manual chase by giving each outstanding document a named owner, a due date and automatic reminders to the client, with an escalation to someone in the office when the deadline is close and the file is still incomplete. Chrysis starts from the client portal or practice software the office already pays for, such as TaxDome or Clio, because its built-in requests and reminders may already cover part of the job, then builds only the missing tracking and escalation as a $3,500 fixed Workflow Fix. No tax or legal judgment is automated, and clients don't have to learn a new portal. ## Pick the handoff that's costing you most. Tell us what gets done by hand, and where, before the next one slips. Fixing hiring and leaving both? Ask about booking them as a pair. You'll get a straight answer on whether it fits, from the firm that would build it. No salesperson in between. [Describe the handoff]() Rather talk first? Call [(770) 649-3525](). ## Not this workflow? Same firm, same written scope and acceptance test. Different job. Practical AI ### Reviewed AI, $4,500 The document pile your team can't keep up with, read first by AI. Anything it's unsure of goes to a person for approval. [See Practical AI]() Infrastructure ### The Infrastructure Fix, $5,500 Fixed before it fails: one defined change, like retiring a server that's out of support, with the rollback tested before anything moves. [See Infrastructure]() Websites and hosting ### The Website Build, $3,500 A site that stops losing inquiries: up to five pages you own outright, with the contact form tested before launch. [See the Website Build]() ### Something else A custom tool, or an integration that broke after an update. Tell us in the form and we'll say straight whether it's ours to solve. [Describe it]() ## Related reading - [Microsoft 365 Workflows for CPA, Law and Engineering Firms]() - [IT Infrastructure and Migration for Engineering, Law \& CPA Firms]() - [Engineering and architecture firms]() - [Specialty and trade contractors]() - [The fine print on IT and AI changes]() - [n8n 2.43.8 Turns Off expression.evaluate Spans by Default]() - [n8n 2.42.7: 'Node not found' in Credential Tests Explained]() - [Dynamics 365 CRM in Teams preview: what to check before a pilot]() - [Power Automate, Logic Apps or n8n for a 40-person CPA firm?]() - [Salesforce or EspoCRM for a small firm's AI workflows?]() --- An engineering-led technology partner for small businesses that need custom software, integration, automation, practical AI and infrastructure, delivered as clearly scoped projects without enterprise consulting overhead. Based in Marietta, Georgia. Remote across the US. Resilience through precision. Microsoft Partner · Pax8 Partner [LinkedIn]() ### Contact - [(770) 649-3525]() - [info@chrysisnetworks.com]() - Marietta, GA 30008 © 2026 Chrysis Networks LLC. All rights reserved. Resilience through precision.