CRM Widgets
The work happens in the record.
So build the tool there.
Most CRM projects stop at fields, stages and reports. But the step that actually decides whether a quote is right, or a job is deliverable, usually happens somewhere else entirely — in a mapping tool, a spreadsheet, or someone’s judgement. A widget brings that step inside the record, where the data already is and the team already works.
The gap
What a well-configured CRM
still cannot do for you.
A CRM is very good at holding the record and moving it through a process. It is much weaker at the moments where someone has to work something out — and that is usually the moment that determines everything downstream.
A rep opens the record, then opens a mapping tool, then a spreadsheet, then a PDF editor — and the finished document never makes it back onto the record.
The quote depends on a judgement nobody can make from a desk, so it waits for a site visit that takes a week to schedule.
Two people quote the same job differently because the method lives in their heads rather than in the system.
Operations receive a job with an address and a price, but none of the reasoning behind either.
The document that proves what was agreed sits in someone’s email rather than against the record.
Reporting is thin because the decisive part of the process happened entirely outside the CRM.
Worked example
A tower-planning widget
for a mobile security company.
Sitewatch deploy mobile surveillance towers to sites that often have no power, no permanent infrastructure and no two layouts the same. Quoting one means deciding where the towers go and what each one can actually see — a judgement that used to need a site visit, and a plan that used to be drawn by hand.
Before
- Site reviewed in a separate mapping tool, outside the CRM
- Tower placements agreed verbally or sketched by hand
- Coverage estimated rather than calculated
- The plan emailed as an attachment, often never filed
- Operations arrive with a price but not the reasoning
After
- The widget opens inside the lead, deal, account or contact
- It reads the site address straight off the record
- Postcode or address lookup locates the site on satellite imagery
- Towers are placed by clicking the map — Master 360° or PID 180°
- Coverage angle and bearing are calculated per device, not guessed
- A placement PDF is generated and attached back to the record
- The plan is saved to the CRM, so the next person sees the same thing
How it is built
It runs on Zoho CRM’s own widget hosting, so there is no separate application to host, secure or log into. The widget reads and writes through the CRM API — pulling the record, discovering the fields that exist rather than assuming them, attaching the finished PDF and saving the plan back against the record. Mapping is Leaflet over satellite imagery, with address and postcode lookup for geolocation; the PDF is generated in the browser.
It stores nothing of its own. Every piece of data it touches lives in the CRM, under the CRM’s own permissions, and the three external services it calls are declared in the widget manifest rather than buried in the code. That matters more than it sounds: it is the difference between a tool your IT function can assess and one it has to take on trust.
The same pattern — read the record, support the judgement, write the result back — is what most in-record tooling comes down to. The map is specific to Sitewatch. The shape is not.
What we build
Six kinds of in-record tool.
These are the patterns that come up repeatedly across sales and operations teams. Most engagements combine two or three rather than building one of everything.
Planning & layout tools
Place equipment, zones or coverage on a real map of the customer’s site, with the geometry calculated rather than estimated. The plan becomes part of the quote instead of an attachment someone has to interpret.
Configure, price and quote
Guided configuration inside the record, with the pricing rules, dependencies and approval thresholds enforced as the rep works. One method, applied the same way by everyone.
Document generation
Produce the survey, plan, proposal or certificate from the record as it stands, and attach it back to that record automatically — so the latest version is always the one in the system.
Address & site intelligence
Postcode and address lookup, geocoding, satellite imagery and travel-distance checks, so the site data on the record is accurate from the first keystroke.
Operational hand-off
Turn a won deal into a scheduled job with everything the delivery team needs: the plan, the access notes, the equipment list and the commitments made during the sale.
In-record intelligence
Put the answer next to the decision. Account history, margin, cross-sell gaps or risk flags rendered inside the record, rather than in a report nobody opens mid-call.
Sales and operations
One tool, two audiences.
The reason in-record tooling pays back twice is that the artefact the sales team produces is the artefact the delivery team needs. Build it once, properly, and the hand-off stops being a translation exercise.
For the sales team
Quote without waiting
Where a judgement previously required a site visit, the rep can often make it from the record — which takes days out of the quote cycle and removes a scheduling dependency.
One method, every rep
The approach is in the tool rather than in the individual, so a new starter quotes the same way as your best person in their first week.
Something to show the customer
A plan, a layout or a configuration produced in front of the customer changes the conversation. It also makes the quote considerably harder to compare on price alone.
For the operations team
The reasoning arrives with the job
Operations inherit the plan and the thinking behind it, not just an address and a figure. Fewer return visits, fewer surprises on arrival.
The record is the single source
Because the output is attached to the record automatically, the current version is the one in the system — not the one in an inbox.
Reportable at last
Once the decisive step happens inside the CRM, it becomes measurable. You can finally see how long it takes, how often it changes, and where it goes wrong.
How we work
From watching the work
to a tool in the record.
Watch the work
We sit with the people doing it. Not a requirements document — the actual sequence of clicks, tabs, spreadsheets and phone calls that make up the task today, including the parts nobody mentions in a workshop.
Find the decisive step
Most processes have one step that sets the quality of everything downstream. A widget earns its place by making that step faster and more consistent, not by wrapping the whole process in new software.
Design inside the record
The widget is designed to live in the record the team already has open, using the fields already there. Nothing is duplicated, and nothing has to be kept in sync.
Build and harden
Built against the platform’s own widget SDK and APIs, with field discovery rather than hard-coded assumptions, so it survives the layout changes that come later.
Prove it on real records
Tested on the messy ones: the record with no postcode, the site that straddles two areas, the job that needs an exception. Edge cases are where in-record tooling either earns trust or loses it.
Deploy and hand over
Packaged, installed and documented. You own the code. Where a widget depends on an external service, that dependency is declared explicitly rather than buried.
Related work
Where this sits alongside everything else.
Analytics & dashboards
Four live dashboard demos you can click through. A widget supports one decision; a dashboard shows you the pattern across all of them.
→CRM consultants
Platform-neutral selection, implementation and migration, with a comparison of every major CRM and a page for each.
→Zoho CRM
Where most of our widget work lands, because the widget and serverless layer come with the licence rather than as an add-on.
→Custom applications
When the requirement outgrows a widget and needs an application of its own, with its own data model and users.
→Connected platforms
Integration work across the systems around the CRM, so the record is complete before anyone builds a tool on top of it.
→Operating model design
Sometimes the decisive step should be removed rather than tooled. This is the work that establishes which.
→Common questions
CRM widgets,
answered plainly.
What is a CRM widget?
A small, purpose-built application that runs inside your CRM — in a record, a related list, a button or a tab — using the CRM’s own data and permissions. It is not a separate system your team has to log into, and there is no second copy of the data to reconcile.
How is this different from a workflow or an automation?
A workflow reacts to something that has already happened. A widget supports a decision as a person is making it. If the step needs human judgement but that judgement needs structure — a layout, a configuration, a priced option — automation alone will not reach it.
Which platforms can you build widgets for?
Most major platforms expose an extension model for this. We build most often on Zoho CRM, where the widget and serverless layer are included in the licence rather than priced separately. We also build against Salesforce, HubSpot and Microsoft Dynamics — see the platform pages under CRM consultants for how each compares.
Do we own what you build?
Yes. The source is handed over and documented on completion, and the external services a widget depends on are listed explicitly so you know exactly what it touches.
What does a widget cost to run?
A widget built on the CRM’s own widget hosting usually costs nothing beyond the licence you already hold. Where one calls an external service — mapping imagery, address lookup, a document service — that service may have its own cost, and we will say so before anything is built.
How long does one take to build?
A focused widget is typically a few weeks rather than a few months, because the scope is one step in a process rather than a system. The constraint is usually how quickly we can get time with the people who do the work, not the build itself.
Which step in your process happens outside the system?
That is usually the one worth building. Book a free discovery call and we will look at how the work actually runs today, and give you an honest view of whether a widget is the right answer or whether something else is.