Each section puts a standard Salesforce page under the build that replaced it. Drag the divider to compare, recreated with invented companies and numbers. Every build runs in production except the deal prediction, which is validated in a full-copy sandbox.
Record pages built around the questions people ask
Standard record pages grow one field at a time until nobody can find anything. We rebuild the Account and Opportunity pages around the questions sales and account teams ask every day, and keep every field one search away.
In production
Unified record page
Both regions of an account on one screen.
Standard: nine tabs and hundreds of fields, four renewal dates, European fields split across two tabs, and the one real meeting buried under automated emails.
A command header with status by region, owners, health, lead score and the seven numbers people ask about.
A field finder that searches every field on the account and edits it in place.
Related lists filtered by region, with glance popups so nobody leaves the page.
The page XML is generated by a script from the live field list, so each field appears once per tab and regional fields never cross.
Lightning Web ComponentsDynamic FormsPython generatorApex
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.
What’s wrong with the standard view
Four renewal dates, one of them labelled with its API name. Which one is right?
Nine tabs, with European fields split across two of them.
The only real meeting is buried under automated emails in the activity feed.
The owner shows the integration user, because the sync wrote last.
Rules live in free-text banners instead of the page itself.
Guided deal page
A stage guide that tells reps what is missing.
Standard: nine legacy stages on the Path, banners standing in for a checklist, and three versions of the same contract fields.
Five real stages with exit criteria, each missing field fixable inline from the guide.
Guidance for every stage, with a target number of days and a flag when a deal stalls.
Header tiles that change with the deal’s phase.
One list of stage requirements drives the guide and the server-side gate, so what the page says is what Salesforce enforces.
Lightning Web ComponentsApex trigger gatesCustom Metadata
1 required to move · 2 needed to send · 1 recommended
Contract approvalRequired to move✎Missing: approver sign-off on a non-standard fee cap
Signer emailNeeded to send✎Still needed from the customer
Contract termNeeded to send✎
Catalog forecast savedRecommended›
✓ Show 6 complete
Guidance for success
Aim for 14 days in this stage. Flagged at 21.Pre-approved clauses go straight onto the order form. Anything past the threshold routes to Finance automatically.
End of page
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.
What’s wrong with the standard view
Nine legacy stages, and the guidance panel is empty.
Four banners say what is wrong. None of them say how to fix it.
Three versions each of the term, fee and signer fields.
Contracts generated from the deal and approved by rule
The order form is built from the deal’s own data, approvals route by clause, and Send stays off until the contract has what it needs. Legal owns the clause library, so the rules change without a deploy.
In production
Contract send
Send stays off until the contract is complete.
Standard: four send buttons, one per template, errors that appeared in DocuSign after the click, and order forms edited in Word and uploaded again.
A readiness list on the deal shows every field and approval the contract needs, each fixable in place.
The order form is generated from deal data and previewed before sending. Word download is off, so changes go through a tracked contract change.
Signed terms are stamped back onto the account, so reporting shows who signed what.
One list of send requirements drives the readiness panel, the disabled button and the server-side check, so the page and the platform never disagree.
Lightning Web ComponentsDocuSign GenApexCustom Metadata
Send ContractPreview Order FormSubmit Contract Change
Send is greyed out until the signer email is added. Everything else the contract needs is in place.
To send this contract, add: • Signer email
Ready to send
Contract term24 months
Billing addressToronto, ON
Signer emailStill needed from the customer
Add
Fee cap of 18 monthsApproved by Finance on Nov 3
Order formGenerated from this deal, version 1
Preview
Order form preview
Order FormNorthgate Surfaces · Renewal 2027
Term
24 months
Platform fee
$1,200 a month
Lead fee
$45 a lead, capped at 18 months
Terms
Standard terms, 2026 edition
Pre-approvedStandard terms, 2026 edition
ApprovedFee cap of 18 months, Finance
Built from the deal’s own fields. Word download is off, so any change goes through a tracked contract change.
DraftedNov 2
ApprovedNov 3, Finance
SentWaiting on signer email
Signed
Terms stamped on the account
End of page
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.
What’s wrong with the standard view
Four send buttons, one per template. The wrong one sends the wrong order form.
Missing data shows up as a DocuSign error after the click.
Order forms are downloaded, edited in Word and uploaded again. Nobody can tell which version was signed.
The approval sits in a queue, and the rep cannot see who has it.
Contract approvals
Who approves what, visible to everyone.
Standard: approval processes live in Setup, visible only to admins. Reps learned the routing when a request bounced.
Every contract clause in one of three lanes: pre-approved, escalates on the number, or always needs sign-off.
The approval chain shown in order, with each hard limit spelled out.
Read live from the Legal-owned clause library, so it never drifts.
Clauses, thresholds and routing come from custom metadata that Legal owns. Adding a clause is a record, not a deploy.
Every row below is read from the clause library when this page loads, so it cannot drift from what the engine does.
Rep adds a provision→Finance→Sales leadership→Executive approver→Legal→Ready to send
Pre-approved2Legal already signed off on this language.
Standard payment termsGoes straight onto the order form
Mutual NDA referenceGoes straight onto the order form
Escalates on the number2Pre-approved inside the threshold.
Fee capmore than 12 months → Finance
Trial periodmore than 60 days → Sales leadership
Always needs sign-off2The clause carries its approver.
Indemnification change→ Legal
Fee waiver→ Executive approver · Hard limit: no more than 6 months
End of page
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.
What’s wrong with the standard view
Approval rules live in Setup. Only admins can see them.
Old and temporary versions sit beside the live one.
The routing is written as a formula, not in words anyone can read.
A revenue prediction on every new deal, with its range
Forecasts used to inherit whatever amount a rep typed. This prediction comes from the brand’s category and catalogue size, shows its range and its comparables, and re-forecasts from real leads after go-live.
Validated in a full-copy sandbox. Not yet in production.
Deal prediction
Predicted leads, revenue and segment, each with a range.
Standard: an amount the rep typed, a probability taken from the stage, and an old model’s figure that mixed full-term and annual values.
Leads, annual revenue and segment predicted from the brand’s category and catalogue size, each with a low and a high.
Similar brands appear beside the number and are never blended into it.
After go-live the forecast re-runs on the brand’s own leads, so every prediction can be checked against what happened.
Backtested against two years of real go-lives before release. The Apex engine is reconciled deal by deal against an independent reference model.
ApexLightning Web ComponentsPython backtestSnowflake
Standard Salesforce
Salesforce, Opportunity details
Example data
OP
OpportunityKestrel Textiles - New business
Forecast
Amount$120,000.00 1Entered by Priya Raman
Probability (%)50 2Set by stage: Value Proposition
Expected Revenue$60,000.00Amount × Probability
Forecast CategoryPipeline
Predicted Term Revenue412,500.00 3Last updated Jul 2025
Predicted Monthly Leads
Predicted Segment
Segment (manual)EnterpriseEdited by Marcus Lee
What’s wrong with the standard view
The amount is whatever the rep typed.
Probability comes from the stage, not from the deal.
An old model’s figure sits beside hand-typed ones. Some are full-term, some annual, and nothing says which.
Feldt Group build
Salesforce, Revenue and segment prediction
Example data
Revenue and segment predictionAt signing, Nov 4Override with a reason
Leads a month118
Low 59 · High 236
Annual revenue$78.1K
Low $46.3K · High $141.8K
SegmentMid-Market
SMB under $72KMid-Market $72K to $180KEnterprise $180K and up
Based onHardwood flooring, 41 brands640 live productsNorth AmericaStandard fees
Similar brands, shown beside the number and never in it
Oakline Floors104 leads a month
Marrow & Grain131 leads a month
Tidewater Plank92 leads a month
After go-liveRe-forecast from the brand’s own leads: 126 a month after three months live.
▸ How this was calculated
Reports and home pages people open every day
Thousands of reports became one hub for leadership, and an empty native home page became one that shows each rep their whole book.
In production
Reporting hub
One tab for every dashboard leadership uses.
Standard: a Reports tab with thousands of reports, copies of copies and folders from people who left, and no way to put custom pages beside them.
A single tab holding the live performance dashboard, the territory heatmap, the review pages and a curated report library.
Pacing against prorated targets, by month and by year, with drill links filtered to each rep.
Adding a page or a report folder is one configuration record.
Driven by custom metadata, with embedded pages sized to the viewport and the report library read live from its folders.
Sales PerformanceAccount HeatmapPipeline ReviewRenewal ReviewReports and dashboards38
As of Nov 6, 9:00
Sales Performance
New customers won in November against each rep’s monthly target. 85% of the year elapsed.
By monthBy year
▲ ExceedingCustomers won in Nov13 / ~11View report
▲ ExceedingTeam vs Nov target118%View report
▲ ExceedingNorth America11 / ~7View report
BehindEurope2 / ~4View report
Reps pacing in November The marker shows each target. Exceeding is over 75%, on track is 50 to 75%, behind is 50% or less.
Priya Raman NA · USDExceeding
4 / 4 · 92%
84% of annual
Marcus Lee NA · USDOn track
3 / 4 · 64%
71% of annual
Sofia Diaz NA · USDOn track
2 / 4 · 58%
60% of annual
Owen Park NA · USDBehind
1 / 4 · 31%
44% of annual
End of page
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.
What’s wrong with the standard view
Copies of copies. Nobody knows which pipeline report is current.
Folders owned by people who left years ago.
Thousands of reports, and the custom pages live in separate tabs.
Optimised native view
A home page that shows a rep their whole book.
Standard: the default Lightning home page, with one mislabelled chart, empty task and event cards, a list of recent items and an admin upload tool.
Six cards with donut breakdowns, chosen, ordered and scoped by each rep.
Click any segment to see the records behind it.
Goals, events and tasks completed in place.
Each card loads independently, so one slow query never blanks the page. Preferences are stored per user.
Good morning, Priya. Here is your book today.⚙ Customize
Close Deals
Open opportunities owned by me, this year
Open $1.42MWon $610KLost $95K
View Opportunities
Deal Hygiene
Stalled = 21+ days in stage
On track 27Stalled 7Past close date 4
View Opportunities
Build Pipeline
New deals this quarter
Early stage 7Proposal or later 4Won 1
View my deals
My Goals · This week
9 of 12 meetings
21 of 30 calls
44 of 40 emails
Today’s Events
10:00QBR · Alder Ridge Tile Co.
13:30Demo · Bramblewood Lighting
16:00Pipeline call
Overdue Tasks
Send revised proposalNov 3
Confirm signer emailNov 4
Book EU intro callNov 7
End of page
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.
What’s wrong with the standard view
The only chart says “by Month” but is grouped by status, and a sixth of it is N/A.
Tasks and events are empty illustrations. Nothing tells a rep what to do next.
Recent items repeat record fields. One owner is a placeholder user called “Disqualified”.
An admin price-book upload sits on every rep’s home page, with an API name in the instructions.
Fifteen tabs in the Sales app, most of which reps never open.
The weekly pipeline call, and metrics emailed to leadership
Managers run the weekly call from one editable screen. Leadership gets the pipeline metrics by email each week, without opening a report.
In production
Weekly call driver
The weekly pipeline call, run from one editable screen.
Standard: a list view where Last Activity was blank on most deals, notes and next meetings sat a click away, and inline edits could not touch the account.
One rep at a time, with last touch, next scheduled and latest note computed from every activity source.
Inline edits write back to the deal and the account, with per-row validation messages.
Stage and close-month filters, stale and past-due flags, and a PDF for the call.
Visualforce with remote actions, sharing and field-level security respected per row, and partial saves that never lose what was typed.
PDFOpen the reportSearch deal or accountSave all (2)
OWNERPriya Raman 4Marcus Lee 7Sofia Diaz 5Former owners (3) ▾
CLOSEAll dates2026OctNovDec2027JanFeb
Account · Deal
Stage
Revenue
Close
Last touch
Next
Latest note
Priya Raman · 4 open deals · $387,700 predicted
Alder Ridge Tile Co. Renewal 2027
Contract Sent ▾
$186,000
Feb 28
Nov 4 · 2d Call: pricing walk-through
Nov 12 · QBR
Waiting on signer email from their legal team.
Save
Kestrel Textiles New business
Proposal ▾
$92,500
Dec 15
Oct 2 · 35dstale Email: proposal sent
nothing scheduled
Asked for a 12-month term instead of 24.
Save
Bramblewood Lighting Expansion EU
Discovery ▾
$48,000
Oct 31past
Nov 6 · today Meeting: intro with buyer
Nov 19 · demo
no note
Save
Coldwater Acoustics New business
Solution Value ▾
$61,200
Jan 30
Oct 28 · 9d Call: budget confirmed
nothing scheduled
Budget approved for Q1.
Save
End of page
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.
What’s wrong with the standard view
Last Activity is blank on nearly every deal.
Next Step says “follow up”. The actual notes are a click away on each record.
Account fields cannot be edited from here.
Every owner in one list, test deals and former users included.
Metrics emailed to leadership
Pipeline metrics in leadership’s inbox, no report to open.
Standard: a report subscription showing seven of 147 rows, with test deals counted as real movement and a link to filter the rest yourself.
Stage buckets with bars, totals and the movement that matters this week.
A line per rep, each name a link to that rep’s deals in the report.
Test records and bulk cleanups excluded, so the email and the report agree.
Scheduled Apex that fails loudly: if the source report changes shape or returns nothing, the owner gets an alert and the job shows as failed.
Audits run by AI agents, then checked against the records
When an audit is too big for a person to read, we split it across AI agents and build the checking in. A second agent tries to disprove each finding, and anything still uncertain goes to a person.
Step 1Batch the workContracts, users or records divided into batches small enough to check.
Step 2Read against rulesReviewer agents apply written rules to every item and cite the evidence.
Step 3Try to disprove itA second agent re-derives each finding with its own queries.
Step 4Resolve and verifyA third agent settles disagreements. Uncertain cases go to a person.
Audits run by AI agents
Audit
Agent design
Scale
Outcome
Signed contract re-read
Reviewer agents in small batches, a challenger on every case and a third agent to settle disagreements. A written rule stopped template wording from being flagged as a modification.
Every signed agreement
Terms loaded with no mismatches on recheck. The re-sign list was limited to the accounts Legal’s rules require.
Regional workflow audit
Domain auditors in parallel, each re-checked by a second pass told to disprove its findings with its own queries. Read-only.
Every regional workstream
Wrong figures corrected, false findings refuted and untracked defects found before anyone acted on them.
Duplicate account clustering
Rule-based clusters first, then agents ruling on each, with an adversarial second audit. Uncertain cases went to a person under frozen merge rules.
The full account base
Duplicates merged with no data lost.
Open-deal family clustering
Graph clustering, then agents on each family, with an adversarial check on every priority family.
Every open deal
Cross-region collisions and data errors found before the cleanup started.
Price-increase history
Agents each given an evidence pack: both contracts, the billed spend and the billing exceptions.
Every derived price-increase record
Wrong records removed, others corrected and missing ones added before the final load.
Security profile consolidation
Analyst agents, refuters and a verifier on the rollback package, with every user’s access compared before and after.
Every user and profile
Profiles consolidated with no user gaining or losing access.
More pages in production
Renewal strategy reviewA quarterly review page grouped by account manager: notice deadlines, estimated current pricing, proposed increase and approval, saved straight to the contract.
Territory heatmapA state map of the prospect book against unassigned accounts, with layer toggles, top states and cities, matched to the exportable reports.
Rep list reviewA live version of a shared prospect workbook: AI fit grades beside each rep’s call, changes since the baseline highlighted, frozen columns and CSV export.
Risk case briefingA live briefing on every at-risk customer, a forking status path, and an executive recap email built from the logged save actions.
Prospects inside the CRMAI-qualified prospects listed in Salesforce with the reasons they qualified, created as the rep’s own account in one click, duplicates caught first.
Catalog forecast editorA quick-action editor for line-level forecasts that rolls totals up to the deal on save.
Talk to us about pages like these for your org.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.