Skip to content

Municipal technology

Technology built around how government actually works.

Bluestone Tech Group builds purpose-made software, information and workflow systems, and AI capabilities for the county and municipal offices that handle government's most detailed work.

Two decades inside probate and court operations taught us the same thing every time: understand the work first, then build the technology.

Our track record

Two decades inside the offices we build for.

For twenty years our software has run the daily operation of probate and court administration — case intake, the cashier's window, the calendar, and the funds a county holds in trust for a child until they turn eighteen.

That work is unforgiving in a specific way. A filing deadline is statutory. An account has to close out to the penny. A record has to still be there in fifteen years when somebody asks for it.

Those years taught us how these offices actually run. They are built out of exceptions, and software written for the straightforward case fails the first time it meets one. The offices we work with already know how they want to operate. They need a system that understands that on day one.

  1. Configured to the office, not the other way round

    Screens, tabs, forms, case types, fee schedules and the data fields an office captures are configuration — held in that office's own database and changed remotely, without reinstalling software or waiting for a release. It is why the answer to "can it do it our way" is usually yes.

  2. Financial controls built for a court, not a storefront

    Receipting, escrow, graduated fee brackets, end-of-day reconciliation and a full sub-ledger for funds held in trust — including interest accrued on a daily balance across multiple banks. This is accounting with a statutory duty attached to it.

  3. A record designed to be defended

    Voided and revised receipts are never removed; the original stays in the record permanently. Material case changes are written to an audit trail. When someone asks what happened three years ago, there is an answer.

  4. The exceptions are the product

    Any system can handle a straightforward filing. The value is in what the office does the rest of the time — the amended filing, the contested appointment, the account that has to close out to the penny. Those cases are why this software exists.

Who we serve

Offices where the details are the job.

Our customers are the organizations that hold the record, take the payment, and answer for both — anywhere in the United States.

  • Probate Courts

    Courts administering estates, guardianships, trusts and adoptions, where the docket and the money have to reconcile.

  • Surrogate's Offices

    Independently elected offices that qualify executors and administrators and hold funds in trust for minors.

  • Register of Wills Offices

    Offices responsible for probate, estate administration and the recording of wills as permanent public record.

  • County Governments

    County administrations modernizing records, workflow and information systems across multiple departments.

  • Municipal Governments

    Municipalities with document-heavy operations and small teams that cannot absorb a failed implementation.

  • Court Administration

    Administrative leadership responsible for case flow, statistical reporting and the integrity of the record.

  • Government Operations Teams

    The people who own the process itself — and who know precisely where it breaks down.

  • Public-Sector Agencies

    Agencies with complex, regulated workflows that general-purpose software has never quite fit.

Our principles

Five things that hold across every engagement.

  • The work comes first

    We learn the operation before we propose the technology. Every engagement starts with how the office actually runs, including the parts that were never written down.

  • Specific beats general

    A narrow tool that fits the workflow is worth more than a broad platform that almost does. We would rather build the right small thing.

  • Built to outlast us

    Public systems run for decades and change hands. We document what we build, transfer what we know, and design so that the next team can take it forward.

  • Candour is part of the service

    We will say when a project is not worth doing, when a system should be left alone, and when AI is the wrong answer. That is more useful than agreement.

  • Enter once, reuse everywhere

    A detail typed at the counter should not have to be typed again somewhere else. Every place the same fact gets re-keyed is a place the record can drift, so we design for one entry and one source of truth.

Contact

Let's talk about your operation.

Tell us what you are trying to improve — a process that takes too long, records nobody can find, a system nobody wants to touch. We will tell you honestly whether we are the right people for it.