Skip to content
SWFL Internal SoftwareContact

Where your customers look instead of calling

Half the calls are the same question: where is my order, my repair, my permit, my invoice. The answer exists in your systems. The customer cannot see it, so they call, and someone stops what they are doing to look it up.

A customer portal is a screen your customers log in to for their order, job, documents and invoices, built for a Southwest Florida business whose phone rings with status questions, in four to six weeks, scoped in writing, in a repository you own.

I read every one and reply within the day. When an off-the-shelf product covers it, I tell you which one and stop there.

  • Built from Fort Myers for Lee, Collier and Charlotte counties
  • A written scope and a fixed price before a line is written
  • Code in your repository, runbook and tests included
  • No vendor pays me, so build-or-buy is answered honestly

Twelve

companies operated, six of them his own, on software he built

790+

products in a catalogue that started at 105, run from one internal tool

15,868

records synced between two systems every run, zero failures

Thirty

live sites generated and shipped from one engine

What it costs to leave it

Every status call is a minute of staff time and a small loss of confidence. A customer who has to ask where things stand has learned that they need to ask. A portal turns that into a login, and the calls that remain are the ones worth taking.

How customer portal gets built here

The starting point

The portal shows what your systems already know: status, documents, photos, invoices, appointments. It is a window, not a second database.

The build

Login is simple and safe. A magic link by email or text. No passwords for a customer to forget and no account for you to support.

What runs by itself

It carries the actions that save calls: approve the quote, pay the invoice, upload the photo, pick the slot, sign the form.

What you own

I run a client platform for a jeweler and an operating system for a vault. The portal pattern here is the one that has been live for years, not a first attempt.

Scope and timing

A customer portal is a four to six week build on top of the systems that hold the data, so it usually follows a job tracking or inventory build, or reads from an existing CRM and accounting package. It includes login, the status views, document and photo access, payments and approvals, and notifications when something changes. For real estate and locating businesses the portal is the transaction checklist the client can see. Built as code you own; a no-code portal is the right call for a business with a simple order and no documents, and I say so when it is.

Straight answers

Do customers really use a portal?
Customers use a portal when it answers the question they would otherwise call about and nothing more. A login that shows the status, the invoice and a button to pay gets used. A login that asks them to manage an account does not.
How do customers log in to the portal?
Customers log in with a link sent to their email or phone, valid for a short time. No password, no account creation, nothing to reset. The link opens their record and only their record.
Can the portal take payments and approvals?
The portal can take payments through your existing processor, approve quotes and change orders, collect signatures and accept uploads. Each action writes back to the system that owns the record, so the office sees it without retyping.

Tell me what is in the way.

A short form and a same-day reply from the person who would write the code. When buying covers it, the reply says what to buy.