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.

Does Lindy work for UK trade businesses?

Lindy can be configured for any vertical, including UK trade businesses, but it doesn't have a native SimPro connector and its domain knowledge is generalist. For a UK trade contractor whose business runs on SimPro and needs an AI Employee that understands trade-specific patterns out of the box, Foreman fits the shape.

Is Foreman cheaper than Lindy?

Foreman pricing is not public during pilot phase. Lindy's site shows tiered SaaS sub-£500/month. According to UK trade industry patterns, the right question isn't the headline price. It's the cost of configuring a horizontal platform for your specific trade context versus running a vertical product that already understands it.

Can I switch from Lindy to Foreman, or run both?

Few prospects sit between the two on the same buying decision because the ICPs are very different. Lindy's typical customer is a generalist SaaS company; Foreman's is a UK trade contractor with 50+ staff. If you're one of the trade directors who's looked at both, the answer is whichever architecture is built for your operation.

What does "vertical" buy a UK trade business?

Domain depth. Foreman doesn't need to be configured to know what a NICEIC certificate, an F-gas log entry, or a milestone gate is. He reads SimPro jobs the way a trades-admin would read them, drafts chases in the technician's own pattern, and escalates to the right office role without configuration.

Foreman vs Lindy: AI Employee for UK Trades

Lindy AI is an AI Employee for any business. Foreman is the AI Employee built for UK trade contractors on SimPro. Two architectures, here's which fits.

Lindy is a horizontal AI Employee platform with 4,000+ integrations, configurable across any vertical, sub-£500/month tiered SaaS, no native SimPro connector. Foreman is a vertical AI Employee built specifically for UK trade businesses on SimPro. Lindy orchestrates across many tools. Foreman understands your trade. He knows what a SimPro estimate is, what a recurring service contract means, why job 4521 matters.

What Lindy is

Lindy and Foreman both call themselves AI Employees. They both live across Microsoft Teams, WhatsApp, email, and phone. They both promise to do the work an admin would do. So when a UK trade director starts looking properly, the two end up on the same shortlist, and the question becomes: which shape fits a trade business actually running on SimPro?

The short answer: Lindy orchestrates. Foreman understands.

Lindy positions itself as an "AI Employee" platform. Their own category language. The shape is a horizontal orchestration layer: a product that connects to other tools and lets you configure agents to coordinate work across them.

Per Lindy's own site, the product is built around:

A broad integration catalogue (4,000+ integrations)
Native channels for Microsoft Teams, WhatsApp, email, and phone
Configurable agents that you build for your specific use case
Tiered SaaS pricing, sub-£500/month at typical tiers
No native SimPro connector

Lindy isn't built for any single vertical. It's a horizontal platform: generalists configure it for their own business; specialist customers configure it for theirs.

If you've been researching "Lindy AI" while looking at what's possible for your operation, this is the shape you've been looking at: broad, configurable, horizontal.

What Foreman is

Foreman is a different shape: vertical, not horizontal. He's built specifically for UK trade businesses on SimPro. He knows what a SimPro estimate is. He knows what a recurring service contract means. He knows why job 4521 matters, why a customer ringing about an invoice on WhatsApp is the same person who chased a quote two weeks ago, and what "good notes" look like for a UK trade contractor's invoicing process.

What he actually does, in director-voice:

He chases the 21-day overdue invoices across email and WhatsApp without anyone asking. He audits NICEIC certificate fields against SimPro jobs and texts the technician 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 cross-source report together from SimPro plus email plus WhatsApp plus phone-log notes. He flags an F-gas register entry that's missing a regulator-required field before the cutoff.

The PM-locked way to put it: Lindy orchestrates. Foreman understands. He knows what a SimPro estimate is, what a recurring service contract means, why job 4521 matters.

He runs the operational layer SimPro stores.

The hero example is the technician notes audit. A job runs in SimPro. Lindy could orchestrate a reminder to send if you configured the rule. Foreman audits the SimPro job, knows what "good notes" look like for the contractor's invoicing process, drafts the chase in the technician's own pattern (because he has seen six months of how they write), nudges them in WhatsApp, and writes the reply back to SimPro when it comes in. SimPro → WhatsApp → SimPro. The orchestration step is the same in both cases. The reasoning underneath isn't.

Three buyer profiles where the vertical answer is the clear pick:

A UK electrical contractor on SimPro, 50+ staff, NICEIC paperwork audit burden. Lindy can be configured to remind a technician to file paperwork if you write the rule. Foreman already knows what an NICEIC certificate is, knows what fields a SimPro job needs for the certificate audit, drafts the chase in the technician's own pattern, and escalates to the right office manager only when the nudge hasn't worked.

A UK HVAC contractor, 60+ staff with three admins, F-gas register pain. Lindy doesn't know what an F-gas log entry is. You would configure it to look for a specific field, fail safely if the field is missing, and notify the office manager. Foreman knows what an F-gas log is, knows what the regulator's cutoff means for the renewal cycle, and runs the audit against SimPro jobs the same way an experienced trades admin would.

A UK fit-out contractor, 80+ staff coordinating milestone sign-offs. Lindy can route a Teams message when a milestone status changes. Foreman knows what a milestone gate is in a UK fit-out context, knows the contract deadline pattern, and drafts the sign-off request to the right project lead from the SimPro job data plus the email and WhatsApp chase history.

Where each lane is

Lindy's lane is horizontal orchestration across a long-tail SaaS stack. Connect, configure, route. Agents you build for your specific use case across 4,000+ named integrations.

Foreman's lane is vertical operations work for a UK trade contractor on SimPro. Read SimPro the way an experienced trades admin would read it. Reason about jobs, customers, quotes, invoices, NICEIC certificates, F-gas logs, milestone gates as the real things they are in a UK trade business, not as generic records in a generic schema.

What Foreman does that horizontal orchestration doesn't:

Skip the configuration tax. Out of the box he knows NICEIC, F-gas, milestone gates, the SimPro job-status vocabulary, the difference between a service contract renewal and a one-off quote.
Compounding institutional memory inside the trade. After 12 weeks he knows which customers query before paying, which technicians reply on WhatsApp at lunchtime, what "good notes" look like for that specific contractor's invoicing process.
Trade-native drafting. The chase to a long-time customer reads differently from the chase to a new-build account; he drafts both.

What horizontal orchestration covers that Foreman doesn't:

A 4,000+ integration catalogue spanning generalist SaaS.
Agent configuration for non-trade business shapes.
Tiered SaaS sub-£500/month pricing.

Who should pick which

If the work that slips through is orchestration across a long-tail of generalist tools without writing code, the lane Lindy sits in is built for that.

If the work that slips through is admin pain that requires understanding trades-specific patterns out of the box, Foreman is built for that. NICEIC. F-gas. Milestone gates. The texture of how technicians actually reply. For a UK trade business on SimPro with 50+ staff, three or more administrators, and that texture of admin pain, Foreman is the closer. Vertical depth, no configuration tax, one persistent identity that already knows the trade.

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

The horizontal lane and the vertical lane don't compete for the same buyer. Few prospects sit between the two on the same buying decision because the ICPs are very different.

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 difference between Foreman and Lindy?: Lindy is a horizontal AI Employee platform, configurable across any vertical, with 4,000+ integrations. Foreman is a vertical AI Employee built specifically for UK trade businesses on SimPro. Lindy orchestrates; Foreman understands. He knows what a SimPro estimate is, what a recurring service contract means, why job 4521 matters.
Does Lindy work for UK trade businesses?: Lindy can be configured for any vertical, including UK trade businesses, but it doesn't have a native SimPro connector and its domain knowledge is generalist. For a UK trade contractor whose business runs on SimPro and needs an AI Employee that understands trade-specific patterns out of the box, Foreman fits the shape.
Is Foreman cheaper than Lindy?: Foreman pricing is not public during pilot phase. Lindy's site shows tiered SaaS sub-£500/month. According to UK trade industry patterns, the right question isn't the headline price. It's the cost of configuring a horizontal platform for your specific trade context versus running a vertical product that already understands it.
Can I switch from Lindy to Foreman, or run both?: Few prospects sit between the two on the same buying decision because the ICPs are very different. Lindy's typical customer is a generalist SaaS company; Foreman's is a UK trade contractor with 50+ staff. If you're one of the trade directors who's looked at both, the answer is whichever architecture is built for your operation.
What does "vertical" buy a UK trade business?: Domain depth. Foreman doesn't need to be configured to know what a NICEIC certificate, an F-gas log entry, or a milestone gate is. He reads SimPro jobs the way a trades-admin would read them, drafts chases in the technician's own pattern, and escalates to the right office role without configuration.