Booking from January 2027
Systems built for people and AI agents.
We build past standard views and workflows: custom, connected systems where your team and AI agents work together.
Systems we connect
Salesforce is often at the centre. The work covers everything it talks to. Pick a system to see what moves between them, and in which direction.
Data and warehouse
Contracts, billing and onboarding
Pick a system to see what moves between it and Salesforce.
Commerce
Sales, marketing and support
AI and team tools
Directions and flows are typical of our engagements. Product names and logos are trademarks of their owners and are shown to identify the systems we work with; Feldt Group is not affiliated with these vendors.
Put AI agents to work across your systems
An agentic enterprise needs agents that read the right record and only do what they are allowed to. We connect the systems, fix the records and set each agent’s permissions. Ask the agent below, before and after that work.
You askWhen does Northgate Surfaces renew?
March 1, 2027.
- Salesforce: Renewal Date (Manual), last edited 2025
Wrong. The signed contract says April 15, so the notice would go out six weeks early.
April 15, 2027. The notice is due by February 14.
- Signed contract, read from DocuSign
- Account record, checked against the contract at 9:00 today
Matches the signed contract.
You askWhich customers did we win this quarter?
Fourteen new customers.
- Salesforce: accounts created this quarter
Nine of them already existed as the other region’s record of the same company.
Five new customers. Nine more are existing customers that opened a second region.
- Identity registry across both regions
- Closed deals this quarter
One record per customer, so nothing is counted twice.
You askUpdate the billing contact for Kestrel Textiles.
Done.
- Ran with a shared admin login
Salesforce changed, billing did not, and the log shows the admin, not you.
Updated in Salesforce and in billing, logged against your name.
- Your own permissions, through a governed connection
- Billing sync confirmed the change
Allowed, because you can make this change yourself.
Example questions and answers with invented data.
Agentforce in Salesforce
Agents inside Salesforce working from cleaned, connected records, with actions limited to what each user is allowed to do.
Claude and AI coworkers
Your CRM and warehouse connected to Claude and other AI coworkers through MCP. Read-only by default, per-user permissions, every query logged.
Agents that audit at scale
Reviewer and challenger agents reading contracts, permissions and records in batches, with a person signing off before anything changes.
Where the numbers stop matching
Every platform keeps its own copy of the customer, and each copy drifts. Pick a problem to see where it starts and what we change.
- Storefront
- Salesforce
- E-signature
- Billing
- Warehouse
- AI tools
Where it breaks
Salesforce, billing and the warehouse each count customers their own way, and nobody owns the definition.
What we change
One agreed definition, synced to Salesforce every hour and checked against the official figures.
Where it breaks
The integration returns a success code while the record on the other side stays the same.
What we change
A reconciliation count on every sync, and an alert to a named owner when a sync goes quiet.
Where it breaks
Terms are retyped between the deal, the contract and the bill, so each copy drifts a little.
What we change
Terms held on the deal record, checked before sending and stamped back onto the account after signature.
Where it breaks
The tool checks its leads against a customer list that covers only part of the CRM.
What we change
An identity registry covering every known customer and prospect, and a guard that stops the run if it loads empty.
Our five practices
Salesforce architecture & engineering
Apex, Flow and Lightning simplified and secured, and documented so your own team can run the org.
You might see
- Two automations fire on the same save and nobody knows which wins.
- A deploy reports success and the change never appears in production.
We deliver
- Org assessment
- Automation consolidation
- Apex & Lightning Web Components
- Security & access
Systems integration
Salesforce connected to your commerce, warehouse, contract, billing and support systems, with one owner for every field and an alert when a sync goes quiet.
You might see
- A metric in Salesforce disagrees with the warehouse and nobody owns the definition.
- An integration has reported success for months while the other side never changed.
We deliver
- Warehouse to CRM
- Commerce integration
- Contracts & e-signature
- Billing & ERP handoff
Data unification & migration
One record per customer across regions and platforms, merged and migrated with a rollback for every change.
You might see
- The same customer exists twice, once per region or storefront.
- A merge is planned and nobody has mapped what the middleware does with the losing record.
We deliver
- Identity resolution
- Merge programs
- Data lineage
- Regional data models
Revenue & contract operations
The deal, the signed contract and the bill kept in agreement, from the first quote to the renewal.
You might see
- Signed contracts carry terms no field in Salesforce can report on.
- Set-up fees or renewal rates disappear between the deal and the bill.
We deliver
- Contract automation
- Contract intelligence
- Pricing & renewals
- Sales process design
AI agents & readiness
Identity, definitions and permissions fixed before any AI agent reads your records, with cost and accuracy measured.
You might see
- An AI pilot produced confident output nobody could verify.
- New leads from a prospecting tool turn out to be existing customers.
We deliver
- Data readiness assessment
- Agent access design
- AI-assisted operations
- Prospecting & scoring
What we build in Salesforce
The same account, as standard Salesforce shows it and as we rebuilt it. Drag the divider across. The showcase has six more.
Information
Additional Information
Fields
Custom Fields 2
Do Not Use - Legacy
Activity
Contacts (40+)
Drag the divider, or focus it and use the arrow keys. Scroll inside the frame: the standard page keeps going, the build stays on one screen. Recreated with example data.
- Custom pages and hubsVisualforce and Lightning pages for reporting, weekly call drivers and quarterly reviews, gathered in one tab.
- Unified record pagesAccount and opportunity pages rebuilt around how people work, with regions side by side and a field finder.
- Tuned standard pagesPath, home pages, list views, compact layouts and report field editing configured so standard Salesforce does more.
- Metrics emailed to leadershipScheduled emails with stage totals, a line per rep and an alert to the owner when the source report changes.
- Contract and approval automationA clause library Legal owns, approval routing by clause and e-signature generated from deal data.
- Audits run by AI agentsAgents reading contracts, permissions and records in batches, each finding checked by a second agent before a person signs off.
- Integrations and pipelinesWarehouse, commerce, billing and support systems connected with one owner per field and alerts when a sync goes quiet.
- Data operations at scaleMerges, migrations and backfills rehearsed at full volume, with a pre-image and rollback for every record.
Engagements start with a two-week diagnostic
You keep the map whether or not we do the build.
- Every system that touches the customer record
- Every integration and automation on it
- Each conflict reproduced on real records
- Its impact in records and revenue
- Fixes ranked by effort and risk
- A findings session with your team
Questions clients ask first
Do you only work on Salesforce?
Salesforce is the core of most engagements, and the work rarely stops there. We connect it to Snowflake, Adobe Commerce, commercetools, DocuSign, Microsoft Dynamics 365, Intercom, HubSpot, Apollo and the other systems that each hold part of your customer.
Can you work alongside our internal team or another partner?
Yes. We work inside your sandboxes, source control and change process, and every build ships with runbooks your team can own.
How do you change production data safely?
Every bulk change gets a full-volume sandbox rehearsal, a pre-image of every record it touches and a rollback file. After release we verify the result record by record against the system itself.
Where are you based?
Toronto, Ontario. We work remotely with teams across North America and Europe, in their time zones.
Talk to us about your systems.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.