hegl for home services
Get more jobs through the office without adding to it.
hegl runs the paperwork and follow-up between a sold job and a paid invoice, on top of the systems you already use.
Onboard your agent
Claude Code
/plugin marketplace add Katch-AI/hegl-plugin /plugin install hegl
Codex
codex plugin marketplace add Katch-AI/hegl-plugin Then install hegl from /plugins. Codex asks you to authorize it in your browser on first use.
Quick start
Start with "list my Hegl organizations", then: /hegl:build [agent] Start building an agent, or pick up where the build stopped. /hegl:feedback [agent] See what people complained about and improve the agent on it. /hegl:fix-errors [agent] Find out why runs are failing and fix it. In Codex and OpenCode, ask in words, e.g. "fix the errors on my agent". Any other MCP client: add the MCP server https://app.hegl.ai/mcp
- Works with the CRM and tools you already run
- Tested on your completed jobs before it touches a live one
- Asks a person when a job does not look right

Use cases
What home services companies run through hegl
Whatever you install or service, the office runs the same loop: check, order, book, tell the customer, get paid. hegl takes the parts that follow a pattern and asks about the rest.
Job intake and work orders
Contracts, measures, photos and notes come in from the field.
hegl checks them against each other, flags mismatches, and builds the work order.
Ordering and procurement
Materials and parts ordered per job, each supplier in its own format.
hegl builds the order from the job file and tracks the acknowledgment.
Scheduling and dispatch coordination
Jobs that can only be booked once the parts, permit or approval is in.
hegl watches for the trigger and books the work when the job is ready.
Permits, inspections and utility paperwork
Every jurisdiction has its own forms, portals and timelines.
hegl prepares the filing, tracks status, and books the inspection.
Financing, rebates and incentives
Conditions and confirmations across several programs and lenders.
hegl chases what is missing and confirms funding before crews commit.
Customer communication
Confirmations, reschedules, delay notices, follow-ups.
hegl sends them off the job’s real status and records the reply.
Service, warranty and callbacks
A customer reports a problem. Someone has to find the job and decide.
hegl pulls the history, checks coverage, files the claim, books the visit.
Recurring service, renewals and collections
Agreements lapse, routes need rebooking, invoices age.
hegl runs the follow-up on schedule and escalates what needs a call.
- Measure vs. contract check
- Change orders
- Lead-time tracking
- Condition chasing
- Funding confirmation
- Permit status
- Inspection booking
- Job confirmations
- COIs and licenses
- Lien waivers
- Completion certificates
- Warranty claims
- Rebate filings
- Service agreement renewals
- Final payment follow-up
- Subcontractor paperwork
Your systems
Nothing to rip out
hegl runs on top of what you already have. Whether that is Salesforce, ServiceTitan, JobNimbus, i360, Jobber or a spreadsheet that works, it stays where it is. Nobody moves data and nobody learns a new system.
No migration.
Your data stays in your systems. hegl reads and writes through the access you give it.
No engineers.
Your office or operations manager describes the work. We connect the systems with you on a call.
No change for your crews.
The field keeps working exactly the way it works today.
The fit
Why this work fits
Same steps every job. A different catch every job.
The path is the same for every job. What changes is what goes wrong on the way. Software could always handle the path. hegl learns the catch from your team, one job at a time.
It lives in your people, not your software.
Your CRM stores the job. It does not know which measure looks wrong or which customer needs the early heads up. Your office manager does. hegl captures that and keeps it.
You already have the answer key.
Every completed job is an example of the work done right. hegl is tested against them before it goes live and after every change.
When it is unsure
What happens when it is wrong
It asks.
When a job does not look right, it stops and brings it to your team with the question. It does not guess.
It remembers.
Every answer becomes a permanent test. It gets better with every job, not worse.
It shows its work.
Every job carries its trail: what was checked, sent, changed, and by whom.
Proof
Work orders at Graboyes

Building a work order used to mean going through the contract and the measure line by line. Now it takes less than half the time. That is a few hours back in my day, every day.

50%+
less time
per work order
Xh+
hours saved
every day
Getting started
How you start
Describe the work.
Your office or operations manager talks it through. hegl writes the spec.
Test on your jobs.
hegl runs against jobs you already completed. You see where it matches your team.
Go live on your call.
It runs alongside your team, asking when unsure. You widen it when ready.
FAQ
Frequently Asked Questions
No. It works on top of it, reading and updating the job in the system you already use.
Your team keeps every decision it wants to keep. hegl runs the routine ones and asks on the rest. Every action is logged to the job.
It is tested on your completed jobs before it goes live, and you see the match rate. Every correction becomes a permanent test. We report a monitored error rate, not a promise of zero.
No. Your office or operations manager describes the work. We connect your systems with you on a call.
A monthly plan that covers building, testing and running your workflows. Unlimited seats. See pricing.
