What CRM does Foreman work with?

Foreman connects to SimPro for jobs and customers, and talks to your team across Teams, WhatsApp, phone and your inbox.

What can Foreman do for my trade business?

Foreman is an AI Employee. He answers anything you'd ask a senior admin, runs the repeatable operations you set up, writes reports better than your CRM does, and watches for issues so your team can act before they become problems. He never contacts customers directly; your team always sends the message.

What's the architectural difference between Foreman and Elyos AI?

Elyos sells six narrow AI agents, each handling one customer-contact task. Foreman is one persistent AI Employee across SimPro, Microsoft Teams, WhatsApp, phone and email. Six configurable bots don't compound institutional memory; one identity does. After 12 weeks Foreman knows your business; six agents each know their own task scope.

Should I pick Foreman or Elyos for my UK trade business?

If your dominant pain is inbound customer-contact volume, the lane Elyos sits in is built for that. Missed calls, slow follow-up, scheduling friction. If your dominant pain is admin overhead growing faster than revenue, Foreman is built for that. Chasing invoices, auditing technician notes, writing reports across SimPro and the channels around it.

Can a UK trade business run both Foreman and Elyos?

Yes. Elyos's lane is customer-contact; Foreman's lane is operations admin. They aren't competing for the same role on your team. If front-desk pain and back-office pain are both real, the two architectures don't overlap.

What does Foreman do that the six-agents architecture can't?

The cross-channel operations work that lives outside customer-contact surfaces. Bulk invoice chasing. The technician notes audit across SimPro and WhatsApp. Custom reporting that spans email and WhatsApp and SimPro. Watch-conditions across every channel. According to UK trade industry patterns, customer-contact pain and back-office pain often co-exist but rarely peak at the same time.

Is the six-agents architecture better for customer-facing comms?

Elyos's materials describe handling around 100 simultaneous calls. The architecture is purpose-built for customer-contact volume. If that is your dominant pain, the lane is built for it.

Foreman vs Elyos: AI Employee vs Six AI Agents

Elyos AI sells six AI agents for trade businesses. Foreman is one AI Employee across SimPro, Teams, WhatsApp, phone and email. Different shapes. Here's which fits.

Elyos AI sells six narrow AI agents covering phone, customer service, sales, appointment confirmation, scheduling, and field engineer functions, focused on customer-contact volume. Foreman is one AI Employee across the whole stack: SimPro, Teams, WhatsApp, phone, email, and the admin layer across them. Two architectures, two lanes.

What Elyos AI is

Two UK-built AI products are being looked at by the same trade-business directors right now. Elyos AI sells six AI agents in the voice and messaging lane. Foreman is one AI Employee across the whole stack. This article explains what each one is, where each lane is, and which fits the shape of your business.

Elyos AI is a London-based, Y-Combinator-backed company building AI for UK trade and field-service businesses. Founded in 2023, they raised $13M in a Series A round in January 2026 led by Blackbird Ventures. Their public site lists Amax (a London fire-and-security firm) as a named customer.

Per Elyos's own product pages, the product is six AI agents, each in a narrow lane:

An out-of-hours phone agent
A daytime customer-service agent
A sales executive agent
An appointment-confirmation agent
A scheduling agent
A field-engineer assistant

The surfaces are voice, email, and messaging. The focus is customer-facing communications and job booking. Their SimPro Marketplace listing is available to SimPro users. Elyos's own materials describe the voice agents handling around 100 simultaneous calls.

If you've searched "Elyos AI" while researching options for your trade business, this is the shape you've been looking at.

What Foreman is

Foreman is one AI Employee, not six agents, not a chatbot, not a workflow builder. A hire who takes briefings, joins your team, and turns up tomorrow. He lives across SimPro, Microsoft Teams, WhatsApp, phone, and email. He reads what your team can read, drafts what your team would draft, and never contacts a customer directly. Your team always presses send.

What he actually does, in director-voice:

He chases the 21-day overdue invoices across email and WhatsApp without anyone asking. He audits every job's notes the moment a tech marks it complete and texts them on WhatsApp if a field is missing. He spots the regular customer who's gone six weeks without booking and flags it to the office manager on Teams. He pulls Friday's report together from SimPro plus email plus WhatsApp plus phone-log notes. He flags an invoice that crosses 30 days while the customer is still actively chasing service over WhatsApp.

The PM-locked architectural line: Elyos sells you six agents. Each one handles a task. Foreman is one person — he handles your business.

He doesn't replace your admin team. He gives them a colleague who never sleeps.

The hero example trade businesses recognise is the technician notes audit. A job runs; the tech is meant to file notes within 24 hours; half the time they don't. Foreman audits every open job in SimPro after the cutoff, finds the ones still missing notes, nudges the tech directly in WhatsApp ("Job 4521: still missing notes, please reply with details"), and writes the reply back into SimPro when the tech responds. SimPro → WhatsApp → SimPro. Cross-channel work, one identity.

Three buyer profiles where Foreman is the clear pick:

A UK electrical contractor on SimPro, 50+ staff, NICEIC paperwork burden. The pain isn't the inbound phone. The pain is the certificate audit across last month's jobs, the invoice chase that lives half in SimPro and half in WhatsApp threads, the Friday report the director keeps meaning to put together. Foreman audits certificates against SimPro, drafts chases in the technician's own pattern, and pulls the report together every Friday from data across SimPro, email, and WhatsApp.

A UK HVAC contractor, 60+ staff with three admins. F-gas register burden, supplier holds in Teams threads, customer comms splitting between phone, email, and WhatsApp. Foreman audits F-gas log fields against SimPro jobs, nudges technicians on WhatsApp before the regulator's cutoff, and chases the supplier in the Teams thread the office is already using.

A UK plumbing contractor, 80+ staff across two depots. 30+ overdue invoices a week, each with chase history spread across email, WhatsApp, and SimPro notes. Foreman audits SimPro receivables, drafts a tailored chase per customer, and tracks the full thread back to SimPro for the office to see.

Where each lane is

Elyos's lane is customer-facing communications. Voice. Email. Messaging. Scheduling. Inbound call handling. Six agents are built for the inbound side of a trade business.

Foreman's lane is the operations layer across SimPro and the channels around it. Admin work that crosses systems. The chase from accounts at the wholesaler. The supplier on hold in the Teams thread. The technician notes that haven't been filed yet. The Friday report you keep meaning to put together.

What Foreman does that the six-agents architecture doesn't:

Cross-channel reasoning across one identity. A customer rings about an invoice on WhatsApp; Foreman knows they chased a quote two weeks ago in email. One memory, every surface.
Compounding institutional knowledge. After 12 weeks he knows which customers query before paying, which technicians reply on WhatsApp at lunchtime, what "good notes" look like on the firm's specific job records.
Admin-side operations work. Bulk invoice chasing. Technician notes audits. Custom reports that mix SimPro and channel data. Watch-conditions across every surface.

What the six-agents architecture covers that Foreman doesn't:

High-concurrency inbound call handling at the volume Elyos's materials describe.
Six customer-contact agents shipped as separate purpose-built products.
A SimPro Marketplace listing.

Who should pick which

If the work that slips through your business is inbound customer contact, the lane Elyos sits in is built for that. Missed calls. Slow follow-up. Unconfirmed appointments. Scheduling friction.

If the work that slips through is office admin across SimPro and the channels around it, Foreman is built for that. Invoice chasing. Technician notes audits. Certificate paperwork. Multi-site supplier chase. For a UK trade business with 50+ staff, three or more administrators, already on SimPro, with admin chaos across the channels around the CRM, Foreman is the closer. One persistent AI Employee, vertical to UK trades, built specifically for the operations layer six narrow specialists can't reach.

If that's not you, this article isn't the one for your business.

Related: Which Foreman is which?: multiple products share the Foreman name. This is the disambiguation source.

Coexistence note

Some trade businesses with both front-desk pain and back-office pain will run both. The two architectures aren't competing for the same role on your team.

Hire him

Founder cohort open · 14 days free. Five slots advertised, five real.

Stop hiring admins to patch the chaos. Hire Foreman.

Hire him →

Common questions

What's the architectural difference between Foreman and Elyos AI?: Elyos sells six narrow AI agents, each handling one customer-contact task. Foreman is one persistent AI Employee across SimPro, Microsoft Teams, WhatsApp, phone and email. Six configurable bots don't compound institutional memory; one identity does. After 12 weeks Foreman knows your business; six agents each know their own task scope.
Should I pick Foreman or Elyos for my UK trade business?: If your dominant pain is inbound customer-contact volume, the lane Elyos sits in is built for that. Missed calls, slow follow-up, scheduling friction. If your dominant pain is admin overhead growing faster than revenue, Foreman is built for that. Chasing invoices, auditing technician notes, writing reports across SimPro and the channels around it.
Can a UK trade business run both Foreman and Elyos?: Yes. Elyos's lane is customer-contact; Foreman's lane is operations admin. They aren't competing for the same role on your team. If front-desk pain and back-office pain are both real, the two architectures don't overlap.
What does Foreman do that the six-agents architecture can't?: The cross-channel operations work that lives outside customer-contact surfaces. Bulk invoice chasing. The technician notes audit across SimPro and WhatsApp. Custom reporting that spans email and WhatsApp and SimPro. Watch-conditions across every channel. According to UK trade industry patterns, customer-contact pain and back-office pain often co-exist but rarely peak at the same time.
Is the six-agents architecture better for customer-facing comms?: Elyos's materials describe handling around 100 simultaneous calls. The architecture is purpose-built for customer-contact volume. If that is your dominant pain, the lane is built for it.