Skip to content

Salesforce consultancy

Anythingis possiblein Salesforce

We build it. Then the power is in your hands.

Book a build sessionBrowse the Academy
Vancouver, British ColumbiaScroll
Counted from source control in one production org. Vendor package metadata excluded.
144,000Lines of platform code shippedApex, Lightning Web Components and Flow, hand-authored, in three months.
190+Automated flows in one orgActive in production, consolidating a whole business onto one platform.
46%Of the Apex codebase is tests144 test classes against 170 production classes.
2Legacy systems retiredA combined ERP and inventory system, and a professional-services system. Zero failed records.

Certified, and the platforms we build on

Salesforce Certified
Sales CloudService CloudField ServiceSalesforce MobileAgentforceApexLightning Web ComponentsFlowVisualforceCustom metadata typesNamed credentialsGemini EnterpriseQuickBooks

01Measured, not estimated

One org, counted line by line

SMT Research consolidated onto Salesforce. This is what was in source control at the end of the third month.

Bar lengths are square-root scaled so the small counts stay readable next to the large ones. The printed figure is the measurement.

Apex classes
314
Apex triggers
32
Lightning Web Components
79
Flows active in the org
~191
Objects under management
119
Custom fields
1,781
Visualforce PDF engines
19
Permission sets
45

Counted from force-app/main/default. Vendor package metadata excluded.

See what was built with it
  1. 01It is all there
  2. 02We find it
  3. 03We build the system
  4. 04Then we hand it over
01

It is all there

Spread across a CRM, two spreadsheets and someone’s inbox.

02

We find it

Every record, counted. No estimates in the first report.

03

We build the system

Apex, Flow, Lightning. Custom where custom is the only answer.

04

Then we hand it over

Your team runs it. That is the whole point of the Academy.

02Why we exist

Three ways a Salesforce build goes wrong, and what we do instead

None of these are implementation mistakes. They are design failures, and they survive every clean deploy.

  • The usual outcome

    Dashboards that present facts

    Most builds list data beautifully and tell nobody what to do next.

    How we build it

    Screens that name the next action

    Every screen passes one test before it ships: does this tell someone what to do in their job today? If it only shows facts, it gets redesigned.

  • The usual outcome

    Forecasts nobody can defend

    A number your CFO has to take on faith, with no way to show how any dollar was placed.

    How we build it

    Every row prints its method

    Installed, invoiced, keyed or estimated, named on the row itself. Every report also says what it does not vouch for.

  • The usual outcome

    AI that invents your numbers

    A confident wrong answer costs more than an honest gap, and it is harder to catch.

    How we build it

    Guardrails named after real incidents

    Every one exists because something went wrong once. We will also tell you when the answer is a lookup and a model would only add cost.

03Numbers say what they are

Every dollar says how it got there

Three systems agreed on the size of the book of work and disagreed on how much of it was done. Every forecast row now prints the method that placed it.

  • Each row carries its method: installed, invoiced, keyed, or estimated
  • A model opinion is never drawn as a progress bar, because a bar reads as a measurement
  • The residue is itemised rather than absorbed into a total
3Systems reconciled into one forecastFound by reconciling three systems that agreed on the size of the book and disagreed on its progress. One org, one reconciliation.
Read the forecast caseContact us to find out more
Sales and Forecasting
How the projection is built
Backlog, remaining to bill on open orders100%
−Marked finished, nothing left to bill24%
=What the engine spreads across months76%
+Open pipeline at 75% or better, not signed2%
=Projected78%
What this number does not vouch for
49 ordersare past their end date and still counted as fully billable, with nobody having marked them finished.
23 ordershave no billing window at all, so their placement is the weakest rule in the engine.
9 orderswere invoiced past their contract value, and each one is named rather than netted off.
Depiction · A revenue forecast that prints its own arithmetic. Every row carries the method that placed its dollar, so a controller can defend the total line by line.The panel on the right is the part most forecasts omit: the amounts the engine will not vouch for, published beside the number rather than discovered in an audit.

04Custom development

We build the screen people run their day from

Every screen passes one question before it ships: does this tell someone what to do next in their job today?

  • Apex, Lightning Web Components, triggers, batch and queueable work
  • Integrations through named credentials, so a key cannot be logged or echoed
  • Configuration over code, so a new rule is a row rather than a deploy
7Kanban boards built on one proven patternTask, work order, purchase order, order, dispatch, production and dev task, plus a real Gantt view. Counted in one production org.
What we buildContact us to find out more
Sales and Forecasting
+ New TaskBoardListGanttCalendar
To do52
+ Add task…
Reconcile PO totals against received stockJun 10
Add change-request number to invoice PDF footerJun 10
Quote follow-up: open quotes with no touch in 30 daysJun 15
Order channels: auto-invite the project managerJun 15
In progress3
+ Add task…
Timesheet hours through to the accounting ledger
Task record page: attachments, subtasks, comments
Done339
+ Add task…
Site survey callNorthern Ltd — VancouverNov 27
Site survey callNorthern Ltd — CalgaryNov 27
Site survey callHarbour Group — SeattleNov 27
Depiction · A custom task board built as a Lightning Web Component, replacing a spreadsheet the team actually ran on. Board, list, Gantt and calendar views over the same records.The add-task field sits at the top of each column, not the bottom. People add work they have just thought of, and scrolling past 52 cards to do it is how a board stops being used.

05Service lines

What we do

Six lines, one operating discipline. Each one links to how it works in detail.

  • 01

    Architecture and consulting

    Someone has to own the whole picture. Data model, automation strategy, sharing and permissions, and an honest audit of the technical debt already in the org.

  • 02

    Custom development

    Apex, Lightning Web Components, Visualforce PDF engines, triggers, batch and queueable work, and integrations through named credentials.

  • 03

    Implementation and migration

    Retire the legacy ERP, inventory or quoting system without losing a transaction. Every record reconciled three ways before anything goes live.

  • 04

    AI and Agentforce

    Conversational agents, models called from Apex, and models in the pipeline. We will tell you when the answer is a lookup and AI would only add cost.

  • 05

    Training and enablement

    Adoption, not software. Workshops and cohort programmes built from your own org, plus self-serve courses in ShareCo Academy.

  • 06

    Salesforce Mobile

    Mobile-safe flows, sign-in and MFA on a device, and adoption by people who never open a laptop. Field work is its own design problem and we treat it as one.

06Salesforce Mobile

The phone is the primary device for half your staff

They open Salesforce in a truck at six in the morning, on one bar of signal, wearing gloves. That is a different design problem to a desktop console.

  • Mobile-safe flows, because the desktop table component does not render in the mobile app
  • Sign-in and MFA failures traced through login history rather than guessed at
  • Adoption checked by signing in as an actual field user, not as an admin
17Field users traced through one sign-in runbookA symptom-to-cause matrix built from login history, verification history and the setup audit trail, over a 30-day window in one org.
Talk to us about field teamsHow we migrate
6:04
Field Operations
Log field activityORD-4192 · Site install
StoppedThis order has no work orders. There is nothing to log, so the flow stops here.
Work orders on this order
0 of 0
Back-date a missed day
Allowed
Minimum rows to continue
1
Back to orderBack-date

Before the fix this screen said: Successfully logged field activity.

Sign-in runbook
Locked out each quarter
90-day expiry on a field profile
Cannot pass verification
Passkey registered on another device
Frozen minutes after login
Threat detection on a VPN address

Mobile app logins never failed in 30 days. Every failure was at the browser login page.

Depiction · A mobile-safe field activity flow and the sign-in runbook behind it. Synthetic order numbers throughout.
Field teams

Bring us the flow that does not work on a phone.

6End users verified againstNamed individuals, each checked under their own permissions.
Contact us to find out more

07Selected work

One account was a fifth of the order book, and nobody could see it

254 orders carried a shipping address. None carried coordinates. The default view had been excluding 89 of them, which mattered more than the map did.

  • 252 of 252 orders geocoded, from a starting point of zero
  • 89 of 254 orders sat in statuses the default view excluded
  • 74 of 74 Apex tests pass, at 89% to 100% coverage across nine classes
20.1%Of the order book sat with a single account51 of 254 orders. Invisible until every order carried coordinates.
Read the sales map caseContact us to find out more
Sales and Forecasting
252 orders · 100% geocoded
Concentration
Largest customer20.1%
51 of 254 orders
Next four combined21.7%
55 orders
Everyone else58.2%
148 orders

Percentages are of order count, not value. The book carries two currencies as entered and is not converted.

Depiction · Every won order geocoded and plotted, coloured by status. 252 of 252 orders placed, from a starting point of zero with coordinates.The largest circle is one customer. It turned out to be a fifth of the entire book, which nobody knew until the map existed. That finding was worth more than the map.

Three systems, and the numbers they moved

All three ran in one Vancouver org. Names withheld, every figure exact.

  • a group of men standing next to each other in front of a building
    Revenue systems
    100%Of the order book geocoded252 of 252 orders placed, from a starting point of zero orders with coordinates.

    The map that found the concentration risk

    Every order geocoded and coloured by status, with a next action on each card. One account turned out to be 51 orders.

    • Default view was hiding 89 orders
    • 74 of 74 tests pass
  • graphs of performance analytics on a laptop screen
    Revenue systems
    3Systems reconciled into one forecastFound by reconciling three systems that agreed on the size of the book and disagreed on its progress.

    A forecast the controller can defend line by line

    Three systems agreed on the size of the book and disagreed on its progress. Every row now carries the method that placed its dollar.

    • 97% of transactions keyed
    • The residue is itemised, not absorbed
  • woman in yellow long sleeve shirt using macbook pro
    Custom development
    31%Of quote lines carried no tax code5,997 of 19,255 quote lines. 5,182 of them sit on Canadian job sites.

    A tax engine rebuilt from 28 configuration rows

    The reported diagnosis was disproved against all 2,335 order line items. The real defect was 5,997 quote lines with no tax code.

    • 28 custom metadata rows
    • Five-phase switchover, any delta treated as a bug
See the full work index

08The method

Seven gates, in order

Each gate stops one failure: shipping a presentation of facts instead of a system that matches how a department works.

  1. 01

    Understand the real operation

    Not the schema. Sources in priority order: the person’s own words, then how the work is actually done today, then the existing data.

    Their words first
  2. 02

    Model the operating system

    Entities, lifecycle, people and cadence. A process model, not a user interface.

    A process model
  3. 03

    Design one surface

    One place the work happens, not another dashboard beside the four that already exist.

    One surface
  4. 04

    Simplify by consolidating

    Add the feature packs each role is missing, then consolidate the surfaces they touch into one. Confusion goes because the work moved, not because something was deleted.

    Something deleted
  5. 05

    Confirm before building

    A document and a mockup, approved. Cheap to change a doc, expensive to change a deployed build.

    A signed document
  6. 06

    Build in verified slices

    Data model first, then thin vertical slices. Never a big-bang build reported as done in bulk.

    A thin vertical slice
  7. 07

    Verify as the real user

    Logged in as them, on desktop and on the phone. If it does not work on the phone, it is not done.

    Desktop and phone
09 / The done rule

Nothing is done until it works for the person whose job it is.

Not an admin check. We match the user’s permission set or log in as them, run the whole flow they would actually perform, confirm they see the right result, then delete every test record we created. If we cannot run that test, we say the work is pending verification. We do not call it done.

Verified against six named end users in the last engagement.

10ShareCo Academy

Everything we teach live is also a course

Training

Learn it from the people who shipped it

Taught from working code rather than slides. Every guardrail in the curriculum is named after the incident that produced it.

  • Four tracks, from Foundations through Agentforce to AI-assisted development
  • Import your own SCORM 1.2 or 2004 packages and run them alongside ours
  • A verifiable ShareCo certificate with a public verification URL
Go to the Academy
Foundations track58% complete

Salesforce Foundations

Courses
12
Assessment
Required
Certificate
Verifiable

A ShareCo certificate is not a Salesforce certification. We say which official exam to sit next.

11Products

The products, and where each one came from

Two came out of systems we built by hand. Four came from gaps we measured in the market. Each card says exactly how far along it is.

  • In build

    Sightline

    AI voice agents for inbound and outbound calls, native to the Salesforce voice data model, at a fraction of the platform price.

    • Voice AI for Salesforce
  • In design

    Sounding

    Regression-test your Agentforce agents before and after every release, so production accuracy stops falling off a cliff.

    • Agentforce accuracy testing
  • In design

    Warrant

    Continuous least-privilege enforcement and audit-ready access reporting, replacing free tooling that admins rate 2.4 out of 5.

    • Access governance
See the product slate

12How we decide

Four calls we made, in our own words

Anyone can show you a logo. These are the decisions themselves, taken from the working notes of a live production org, including the one we chose not to deploy.

  • “Any delta is a bug in the mapping, not an improvement.”

    The regression rule for the tax switchover. Sum the tax over every order item, deploy, re-run, and treat any movement as a defect until proven otherwise.

  • “An org-critical integration cannot depend on one laptop being awake.”

    Written after a scheduled sync stopped silently for twelve hours with exit code zero. It moved to hosted infrastructure with a heartbeat and an hourly watchdog.

  • “Does this tell someone what to do next in their job today?”

    The one-line test every screen has to pass before it ships. If it only shows facts, it is wrong and it gets redesigned.

  • “Not deployed. It changes a customer-facing contract value, so the controller should confirm first.”

    A a material amount sign error found on one progress claim, fully diagnosed and fully designed, and deliberately held back for a human decision.

We will walk you through the org itself, screen by screen, and you can ask the people who run it every day.

13Questions

Before you call

Ask us directlyWe answer in writing within one business day, before any money changes hands.
Start here

Bring us your hardest Salesforce problem

Tell us what is broken and what it is costing you. You get a written read on it within one business day, whether or not you hire us.

Book a build sessionSee the work
  • Reply within one business day
  • hello@shareco.ca
  • Vancouver, British Columbia