A hand drawing a site structure on a whiteboard in red marker

Solution

You own it outright, including the right to take it elsewhere

Lighthouse is our own content and membership platform. Every build starts from a base we maintain and becomes a system shaped around how your organization actually works — licensed to you for a one-time build cost, with no recurring platform fee and no obligation to keep working with us.

  • more than 20 years

    that our longest-standing clients have run on Lighthouse

    Clients who start on Lighthouse stay on it, and some have run their business-critical systems on it for more than two decades.

The problem

The license you keep renewing

Most organizations running a membership database and a public site are renting the platform underneath both. The fee arrives every year whether or not the features it covers are ever switched on, and it rises on a schedule set by the vendor rather than by anything happening in your organization.

The second cost is subtler. Upgrades come when the vendor decides, the interface and the data layer move together whether you wanted both touched or not, and the longer the platform runs the more expensive leaving becomes. That is not an accident of the model — it is the model.

What this covers

What you get

  • A build shaped around your processes

    Every engagement starts from a base platform we keep current and becomes a heavily customized system for your organization. You are not configuring your way around someone else's assumptions about how membership works.

  • Content and membership in one system

    The public site and the member data behind it run on the same platform, so the integration work that usually sits between a CMS and a CRM is not work at all.

  • Decoupled, API-based architecture

    Interface, middle layers and database are separate. The front end can be rebuilt or redesigned without touching the data underneath, which is what makes a redesign a project rather than a migration.

  • Built on ASP.NET with an Azure SQL backend

    A stack your own developers can hire for and read, rather than a proprietary templating language that exists only inside one vendor's product.

  • Hosted where it suits you

    On your own servers or in the cloud. Where the system runs is your decision, not a condition of the license.

  • Upgrades carried through, not forced

    We keep the base platform current with new releases and bring client builds forward with as little disruption as the change allows.

What you gain

Why it is worth it

  • One build cost, not an annual fee

    You pay to have it built. There is no recurring platform license, no per-seat charge and no renewal conversation.

  • You own it, in full

    The build is licensed to you and owned by you. If you want to take it to another firm, you can, and you do not need our permission or our cooperation to do it.

  • Redesign without re-platforming

    Because the interface is decoupled from the data, refreshing how the site looks does not mean rebuilding what it runs on.

  • Nothing you are not using

    You are not carrying the cost of a feature set built for the largest customer on the vendor's list.

Fit

Whether this is for you

  • Who it is for

    Associations and member organizations running a public site and a membership or content database that have to agree with each other — particularly where the processes behind them are specific enough that configuring a standard product means working around it.

  • Who it is not for

    If you need a straightforward marketing site with no membership, no content operation and nothing to integrate behind it, this is more platform than the job needs and we would tell you so.

Before you ask

Questions we hear

What happens if we stop working with you?

You keep the platform. It is licensed to you and owned by you outright, and you are free to take it to another firm to maintain or extend. We think that is the right arrangement even though it means we have to earn the next engagement rather than rely on a renewal.

Is Lighthouse a product or a custom build?

Both, in sequence. There is a base platform we maintain and improve across all our clients, and every engagement starts from it. What you end up running is a version customized to your organization, which is why two Lighthouse builds can look and behave very differently.

Where does it run?

On premise on your own server, or in the cloud. It is built on ASP.NET with an Azure SQL backend, and the hosting decision is yours to make and to change.

How do upgrades work if every build is customized?

We keep the base platform current as new releases land, then bring each client build forward from it. The decoupled architecture is what makes this tractable: an interface upgrade does not require the backend to move at the same time.

Want to see it running?

We can show you what this looks like on a system close to yours, rather than a demo built to look good.

Contact us

Start a project

Nothing here is required except an email address and enough detail to reply usefully. The more you tell us, the better the first answer.

If you do not know, leave it. We will work it out.

What you run, what is not working, and roughly when you need it fixed.

No need to prepare a brief. A few honest sentences gets a better first reply than a polished one.