LockPoint Start a systems audit

Business systems engineering

We engineer the system
between demand and revenue.

Growing companies run on tools that don’t talk to each other, so their people become the integration. We find where that leaks leads, hours and visibility, then engineer the missing system around the business.

Start a systems audit See the work
How one enquiry moves through a connected business system Instagram, the website, the phone, email and referrals all feed one capture point. From capture the line runs to qualify, then across a missing segment to the record, the staff who work the queue, a booked job and revenue. The missing segment is the gap between the tools; the lockpoint is the layer LockPoint builds to close it. Demand Instagram Website Phone Email Referral Lost The gap · nobody owns this LockPoint builds the missing segment The lockpoint · connected Capture 01 · One door Qualify 02 · Ranked Record 03 · One record Staff 04 · In order Booked 05 · Logged Revenue 06 · Reported How one enquiry moves through a connected business system Instagram, the website, the phone, email and referrals all feed one capture point. From capture the line runs down to qualify, then across a missing segment to the record, the staff who work the queue, a booked job and revenue. The missing segment is the gap between the tools; the lockpoint is the layer LockPoint builds to close it. Demand Instagram Website Phone Email Referral Lost The gap · nobody owns this LockPoint builds the segment The lockpoint · connected Capture 01 · One door Qualify 02 · Ranked Record 03 · One record Staff 04 · In order Booked 05 · Logged Revenue 06 · Reported
  1. 01Today. Enquiries reach the gap between two tools and wait. Some are answered late. Some are never seen. This is where growth leaks.
  2. 02The build. LockPoint engineers the missing segment: the routing, the record and the reporting no vendor sells, because it only exists for your business.
  3. 03Connected. The same enquiry moves on its own, all the way to revenue, without anyone having to remember to move it.
First published build
Frenchy Smiles — cosmetic dental practice, Atlanta
What we delivered
Multi-page site, custom staff CRM, lead capture on AWS
Status
Site live. CRM built and staged, not yet carrying real patients; launch held until the vendor BAAs are signed.

01 — The problem

Your staff
are the
integration

Your business shouldn’t run between ten disconnected tools. Most do. Each one is fine alone. Between them sits a person doing copy and paste — and that person is the integration layer. That is where the leads, the hours and the visibility go.

Ten business tools, all connected through one person Instagram, the website, forms, the phone, email, the CRM, scheduling, payments, spreadsheets and reporting arranged in a ring, each wired only to a single person in the middle who carries information between them by hand. Instagram Website Forms Phone Email CRM Scheduling Payments Spreadsheets Reporting One person The integration layer, today Ten business tools, all connected through one person Instagram, the website, forms, the phone, email, the CRM, scheduling, payments, spreadsheets and reporting listed down the left, each wired only to a single person on the right who carries information between them by hand. Instagram Website Forms Phone Email CRM Scheduling Payments Spreadsheets Reporting One person Does every join
01

Enquiries land in four places Lead loss

A form, an inbox, the phone, and DMs. Nobody is certain which one holds the newest, so some are answered in minutes and some are never seen at all.

02

Follow-up runs on memory Revenue

Whether someone gets a second call depends on whether a person remembered. The ones who needed two calls are the ones you lose.

03

The same information is retyped daily Hours

Out of the form, into a spreadsheet, into the calendar, into the billing tool. Every retype is time spent and a chance to get it wrong.

04

Nobody can see the pipeline Visibility

You can find out what happened last month. You can’t find out what is happening this afternoon without asking three people.

05

Customers repeat themselves Experience

They told the form, then the phone, then the person at the desk. Each tool knew a piece; none of them knew the customer.

06

The website undersells the price Positioning

The service costs five figures. The site looks like it cost four hundred dollars. People decide before they ever speak to you.

You almost certainly don’t have all six. One or two, costing real money every week, is usually enough to justify building something.

02 — The operating layer

We don’t sell you
another tool.

Almost nobody is missing software. What’s missing is the layer between the tools — the part no vendor sells, because it only exists for your business.

We study how work actually moves through the operation, then engineer that layer: capture, routing, the record, the automation and the reporting, connected end to end and built around the tools you already run. Not a deck describing it. The system itself, built to be installed in your business, with your team trained on it, and yours to keep.

CaptureEvery enquiry lands in one place, in one shape.
RoutingThe right person, by rule, in minutes.
Follow-upSecond and third attempts that don’t depend on memory.
VisibilityWhat is happening this afternoon, on one screen.
EfficiencyNothing typed twice. Nothing carried by hand.
ExperienceNo customer asked to repeat themselves.
ConversionThe ones who needed two calls get two calls.
ReportingThe numbers you run the business on, current.

03 — Capabilities

One system.
Seven layers.

Not seven services to pick from. These are the layers of one operating system, in the order an enquiry passes through them. Each one names the capability that builds it.

01

Capture One front door

Every enquiry — the DM, the form, the phone, the referral — lands in the same queue in the same shape, with its source recorded, and nothing depending on who happened to be looking.

Lead capture systems & websites
02

Route The right person, in the right minute

An enquiry reaches whoever should act on it by rule, not by whoever notices first. Speed to first contact is the one number almost nobody is actually managing.

Speed-to-lead & routing
03

Record One copy of each enquiry

A pipeline shaped like your actual sales process, holding one record that everything else reads from — not a generic deal board you bend your team around.

Custom CRM
04

Automate The work nobody should do by hand

Sorting, drafting, summarising, the second and third follow-up — handled automatically, with a person still deciding what matters and an off switch they can reach.

Follow-up, workflow & AI automation
05

Operate The screen your team lives in

Built for the four things they actually do all day instead of the forty they don’t: a queue, a job board, an approvals list, a dispatch view.

Internal tools
06

Connect The tools you keep, in step

Integrations that hand work between the systems you already pay for — and a straight answer where a vendor has no usable API, rather than something fragile built on a workaround.

Business integrations
07

See This afternoon, not last month

The handful of numbers you run the business on, on a screen, current — without someone exporting to a spreadsheet every Monday morning.

Reporting & dashboards

Few businesses need all seven layers. The audit decides which ones matter for yours, and in what order.

Every capability

04 — Proof

Frenchy Smiles

A porcelain veneer practice in Atlanta with an Instagram following, no website, and a Google Form for a booking system. We built the site, then the system behind it. The same enquiry, drawn before and after.

Public site
thefrenchysmiles.com
Live
Eleven-page website, structured intake on every page
Built and staged
Staff CRM and call queue, on the practice’s own AWS account
The live Frenchy Smiles home page: a dark editorial layout with a 3D porcelain tooth and the headline ‘Porcelain, made to your face’.
Fig. 01The public site — live at thefrenchysmiles.comOpen it and check

Before

The enquiry

  1. Interest arrives from the practice’s Instagram following.Source
  2. The link in the bio goes to a Google Form.Capture
  3. The form drops the submission into a spreadsheet.Record
  4. Whether anyone calls back depends on who reads the sheet.The gap · nobody owns this
  5. Patient details end up in whichever tool touched them last.Data
  6. No view of what is waiting right now.Visibility

After · site live, CRM staged

The same enquiry

  1. Interest arrives from the same Instagram following.Source
  2. An eleven-page site answers what a patient wants to know first.Capture · website
  3. Structured intake on every page posts to one endpoint, every attempt logged.Route · intake API
  4. Contact details land in a separately encrypted vault.Record · sealed store
  5. The front desk works a call queue ordered by who has waited longest.The lockpoint · call queue
  6. The outcome is logged in one keystroke and the next one is up.Operate · one key

The website half of this is live and public — the Google Form has been retired. The CRM half is built and staged: it has not yet run with real patients, because launch is held until the vendor Business Associate Agreements are signed. Every screenshot runs on demonstration data.

The Frenchy Smiles CRM in a browser: a left sidebar with the call list, a middle column listing waiting enquiries ordered by wait time, and a detail panel showing one record with contact details hidden behind Reveal controls, a history of call attempts, and outcome buttons.
  1. 1The queue. Every source, one list, longest wait first.
  2. 2Sealed contact details. Behind a Reveal control; each opening is recorded.
  3. 3Every attempt, dated. A new staff member picks the conversation up cold.
  4. 4Outcome in one keystroke. Number keys one to five, then the next one is up.
  5. 5Source on every record. Instagram, web form, phone or referral, logged at capture.

Fig. 02The staff CRM — built and staged, not yet liveDemonstration data

Read the case study

05 — How we work

Five moves

Five moves, in a fixed order. The first two can end with us telling you the build isn’t worth doing yet — and the audit is where that gets decided.

01

Diagnose

We follow the work through your business — where enquiries land, what gets retyped, which handoff drops things, which tools have a usable API.

You get the leaks, named and estimated
02

Map

The System Map: a written document of where the operation leaks, what closes it, what it takes to build, and in what order. Useful whether or not you hire us.

You get the System Map
03

Build

Written to a fixed spec and a fixed date, in stages you can look at as they land. Nothing is a surprise at the end because you have seen it the whole way.

You get something to look at, every stage
04

Connect

It goes into the real workflow, with your data, your people and the tools you keep. We train the staff who will be in it every day.

You get a working system, in your name
05

Optimize

On a retainer the system never sits still: changes almost daily in the first weeks while it beds in, then an optimization pass over everything we run for you — usually every month, never less than once a quarter.

You get a system that keeps improving
How a build runs, in detail

06 — Straight answer

Custom isn’t automatically better

It is better in specific conditions and a waste of money outside them. Here is where the line sits, so you can work out which side you are on before you talk to us.

Buy off the shelf

  • Your process is close enough to standard that you can adopt the tool’s way of working without much pain.
  • You need it running next week, not next quarter.
  • The tool’s subscription is small next to what a build would cost to write and keep.
  • Your volume is low enough that a person doing the joins by hand is genuinely cheaper.

Build the layer

  • You are paying staff to bridge the gaps between tools every single day, and the cost of that is now real money.
  • The way you work is the advantage, and standard software makes you give it up.
  • You have compliance, privacy or audit requirements the generic tool won’t meet.
  • You are paying per seat for software where your team uses four of its forty features.

07 — The guarantee

Built to spec.
Live on schedule.

We guarantee what we control. The build matches the spec we agreed in writing, it ships on the date we set, and it does what the spec says when it lands. If we miss that date for a reason that belongs to us, you don’t pay for the overrun. Paperwork that belongs to you or a vendor — a signed agreement, an API you have to be granted access to — sits outside the date, and we say which parts those are before anything starts.

We do not guarantee lead volume, revenue or conversion rate, because those depend on your market, your offer and your team — three things we don’t control. Anyone who promises you a number for them is guessing, and you will be the one who finds out.

Everything we build is yours: the code, the data and the accounts, in your company’s name. If we part ways, it keeps running and someone else can pick it up.

08 — Questions

Before
you ask

The six that come up on nearly every first call.

What does LockPoint actually build?

Software. Specifically: custom CRM systems, lead capture and routing, automation for repetitive work, internal tools your staff use daily, integrations between systems that don’t currently talk, and the websites that feed all of it. It is written for your business rather than configured from a template.

Do you replace the software I already have?

Usually not, and we’ll say so early if replacing something would be a mistake. On the Frenchy Smiles build the practice’s clinical records system and phone system both stayed exactly where they were — we built around them. We replace a tool only when keeping it costs more than removing it.

Can you integrate with what we already run?

Often, but not always, and the honest answer depends on the tool. Some vendors publish an API anyone can use. Some gate it behind a partner agreement. Some have nothing at all, in which case we will tell you that rather than quietly building something fragile on top of a workaround.

What does a project actually involve on your side?

Time from the people who know the work. The diagnosis stage needs a few conversations with whoever handles enquiries and whoever runs operations. During the build we come back with things to look at. At install, your team needs an hour or two of training. Beyond that we stay out of your way.

Do I own what you build?

Yes. The code, the data and the accounts are yours, and the infrastructure is set up in your company’s name where that is possible. If you and LockPoint part ways, the system keeps running and someone else can pick it up. We’ll put that in writing before anything starts.

Is there ongoing support after handover?

Available, not compulsory. Clients on a retainer get a standing optimization cadence: changes almost daily in the first weeks while the system beds in, then a pass over everything we run for them — the site, the CRM, the automations — usually every month, and never less than once a quarter. Others take the handover, run it themselves and come back when they want the next thing built. Both are fine. What a retainer costs depends on the system, and we quote it against the real thing rather than a price list.

Next step

Find
the gap.

The audit is a short piece of work: a few conversations with whoever handles enquiries and whoever runs operations, then we follow the work through your tools. It ends in a System Map — where your operation is leaking, what a system would close, what it would take to build, and in what order. Sometimes it concludes that you don’t need us yet. You get told that too. How long it takes depends on the size of the operation, and you have the scope in writing before it starts.

Start a systems audit team@lockpointgrowth.com