// AI consulting
Your own AI engine and AI team.
A server you own and two senior builders on call. It takes the routine work off your managers' plates around the clock, across every system you run, and your managers approve the results.
406
bid invitations screened
154,768
plan pages read
187
priced proposals sent
6
live products we built and run. See them →
Our own five-person contracting company runs on the system we install. Counts are from the Majic platform for July 31 to September 30, 2026. A person approved everything that went out.
Summary
The plan in three points
-
The routine work is where the hours go
Sorting messages, chasing paperwork, drafting the same proposals and reports. Today nothing does that work at night, or for every account at once.
-
A server you own does it
It reads your systems, drafts the work and ranks what needs attention. Your managers approve the results before anything goes out.
-
It is yours, not rented
It is not a seat in someone else's program, and every company you own can use it. Start with a three-week discovery.
How it works
Managers ask, and your server answers.
Managers reach the chat on a phone or a computer through an encrypted, sign-in-protected link. The engine reads your systems, answers in the same chat, and keeps its working copy on your server.
One engine connects every system you run: CRM, email, accounting, the support desk, outreach, files and floor plans, and hiring.
And while you are asleep
Your engine is on the night shift.
- 11 p.m.
It reads the night's messages and notes.
- 3 a.m.
It checks contractor paperwork and scores accounts for risk.
- 7 a.m.
Every manager has a ranked list with draft replies, before the first phone rings.
Sales
“Draft yesterday's survey proposal.”
A proposal draft from the survey notes or floor plan, the same day.
Operations
“What came in overnight?”
Overnight messages sorted by urgency and routed to the right manager.
Accounting
“Which invoices are 45 days late?”
Overdue accounts ranked, with a reminder drafted for each.
Owner
“How did each location do against plan?”
One brief across every company: cash, sales and what needs a decision.
Illustrative examples. Discovery confirms each workflow and the systems behind it.
Your roles
The engine takes tasks straight from your job descriptions.
We start from the work your people are already hired to do, and give each role a measurable goal.
| Role | The routine work | What the engine does |
|---|---|---|
| Sales, outreach | Calls, emails and visits every day, each one logged in the CRM. | Researches each prospect, drafts the emails and logs the notes. |
| Sales, proposals | Survey the site and turn the notes into a proposal. | Drafts the proposal from the survey notes the same day. |
| Operations | Inspections, complaints and a nightly recap. | Writes the recap from the day's entries and routes urgent items by 7 a.m. |
| Vendors | Find a trusted vendor who is free. Keep insurance certificates and W-9s current. | Matches each job to a vetted vendor, drafts the work order, tracks expiry and chases renewals. |
| Billing | Keep customer and contractor billing current. | Matches invoices, ranks overdue accounts and drafts reminders. |
| Controller | Close the month faster. | Drafts the financial package with variance notes before review day. |
| Hiring | Screen applicants and book interviews. | Screens applicants against the posting and books the interviews. |
Examples to confirm in discovery. A manager approves every result.
Why your own
Your own engine, not a seat in a program.
A per-seat AI subscription helps one person, when that person asks. Your own engine works for the whole company.
| Per-seat AI subscription | Your own engine and team | |
|---|---|---|
| Who sets priorities | The vendor, for every customer | You do: your priorities and your schedule |
| When it works | Mostly when a person asks | Around the clock, including the night shift |
| What it reads | The email and files one user can open | CRM, accounting, support and hiring together |
| Where records sit | The vendor's cloud | A server in your building that you own |
| What growth costs | A fee for every user, every month | A fixed cost; more work adds no fees |
| Who builds for you | A shared help desk | Two builders who know your business |
| Who can use it | The users you pay for | Every company you own |
Yours, not rented. If you already license an AI assistant, keep it. Your own engine does the work that a per-seat tool is not built for.
Step one
What discovery delivers in three weeks.
Discovery is a separate fixed fee, quoted in writing. It replaces estimates with your own numbers before you commit to anything larger.
Listen
One hour with each manager on sales, vendor, night and billing work. One site visit is included.
Measure
A read-only review of your systems, and baseline numbers pulled from your own records.
Recommend
We present the server, its goals and a fixed price to you and your leadership.
What you receive
- Baseline numbers from your own records
- A systems report and the approvals needed
- A staff AI policy your people can use today
- A measurable goal for each role
- Return and payback rebuilt on your numbers
- A fixed price for the server and the build
Our promise
The report is yours either way.
If your numbers do not show a two-year payback, we say so and you stop after discovery. To do the work we need a sponsor, manager interviews and read-only access.
The plan
Seven milestones, three of them your decision.
Discovery is a separate fee, and its report is yours to keep. The server is paid when the tier is chosen, and the build half then and half at go-live. Maintenance and support is billed monthly for one year from go-live.
A typical schedule is shown here. Yours is fixed in the discovery report.
- Week 0Your decision
Buy discovery
Interviews, baselines and a fixed price.
- Week 3Your decision
Choose the server tier
Our recommended tier and its goals.
- Week 6
Server built and installed
Ordered, assembled and tested on site.
- Week 12
Go-live: the support year starts
The first three roles working in the chat.
- Month 6
First quarterly review
Results measured against the goals.
- Month 8
All roles live
Managers trained on their daily tools.
- Month 15Your decision
Renewal decision
One year of results against the estimate.
Safety and security
Four real cases, and the safeguard each calls for.
AI goes wrong in predictable ways. Each of these is public record, and each maps to a control we put in place from day one.
| Case | What happened | Safeguard it calls for |
|---|---|---|
| Samsung, 2023 | Engineers pasted confidential source code into ChatGPT. Samsung banned the tool. | One usage policy, and a safe tool so staff skip public ones |
| Air Canada, 2024 | Its chatbot gave a customer the wrong refund terms. A tribunal held the airline liable. | Human approval before anything reaches a client |
| Microsoft 365 Copilot, 2025 | A flaw let one crafted email pull internal data out through Copilot. Microsoft patched it. | An owner for AI settings, patches and updates |
| McDonald's hiring chatbot, 2025 | A vendor password of 123456 exposed the records of up to 64 million applicants. | Vendor vetting, and access limited by role |
Your sponsor owns the rules. Majic AI runs them day to day. Records stay on your server with backups, and every request is logged and reviewed each month.
Sources: Bloomberg, May 2023; Moffatt v. Air Canada, 2024 BCCRT 149; Aim Security, CVE-2025-32711, June 2025; Wired and Krebs on Security, July 2025.
Why Majic AI
Your own AI team: two senior builders on call.
A team, not one hire. There is no salary or benefits to carry. If we are ever unavailable, you keep the server, the data and a written runbook for every role.
Nathan Morris
Chief Technology Officer
- 12 years in healthcare IT: 600+ hospital projects in 50 states
- Seven years as Director of IT and Sales Engineering
- Primary developer of Majic
Mike Meyers
Co-developer and platform administrator
- 27 years in healthcare IT, network architect to chief architect
- Helped build an IT services firm from startup to sale
- Ran 200+ servers for large hospital systems
Proof
Our own five-person contracting company runs on Majic.
August and September 2026. The same design is proposed for you: the engine reads, counts and drafts, and a person approves what goes out.
406
bid invitations screened
154,768
plan pages read
187
priced proposals sent
2
people who built it
Counts are from the Majic platform for July 31 to September 30, 2026.
Beyond one company
One engine, one team, every company you own.
Each added company is a connection project, not a second server or a new hire, and its records stay separate. A property group gets leases and renewal dates tracked. A development group gets contractor bids compared line by line. The owner gets one Friday brief across all of them: cash, sales and the items that need a decision.
Two-minute self-check
Is your company ready for this?
Tick what is true today. Nothing is sent anywhere. The two things that matter most cost nothing: a written rule for staff, and one named owner.
Your score
0 of 8
Start with the policy and one named owner. Those two cost nothing and make everything after them safer.
Straight answers
The questions we get first
We already pay for Copilot or ChatGPT. Do we need this?
Keep it. It is good at one person's inbox, documents and meetings, and it works when that person asks. Your own engine does the jobs it is not built for: reading across your CRM, accounting and job records together, working overnight, and drafting for a manager to approve. Plenty of companies run both.
Do we have to buy a server?
No. You decide on a server only after discovery, when you have seen your own numbers, and the discovery report is yours either way.
Where does our data go?
With a server at your site, your records stay on it, with backups, and every request is logged and reviewed each month. With the hosted option it runs on servers we own and operate, not on a public AI service. Either way, managers reach it through an encrypted, sign-in-protected link.
What if the AI gets something wrong?
It will, sometimes. That is why a person approves anything that goes to a customer, and why the engine flags a gap instead of guessing. We build the approval step in from day one and it does not come out.
How long until it is doing real work?
On a typical schedule: three weeks of discovery, the server built and installed around week 6, the first three roles working at week 12, and all of them by month 8. Your schedule is fixed in the discovery report.
You are two people. What if you are not available?
You keep the server, the data and a written runbook for every role. Nothing about the system depends on a login only we hold.
What does it cost?
Every engagement is priced in writing before work starts. Most companies begin with a pilot on one job, so you see the result before you commit to more. Book a call and we will send the price.
Next steps
A small first step.
Start with the three-week discovery
A fixed fee, in writing. The report is yours either way.
Name one sponsor
And the managers for the first three roles.
Decide on the server later
Only after you see your own numbers.