forge

Five systems in production

Software I build,
and then run.

Two products of my own, an advertising service with paying clients, and two platforms in daily use inside a national mortgage lender. Designed, written, deployed and operated by one person.

Operating since
January 2024
Built by
One person
Based in
Birmingham, Alabama
Third-party scripts
None

Selected work

Five systems,
all of them in use.

Three you can open in a new tab right now. Two were built for a client and cannot be linked, so they are shown here running seeded demonstration data instead.

Product 2026

BizForge OS

The quote prices itself from the sketch.

Quoting, scheduling, invoicing, phone and an AI receptionist for home-service contractors, in one app.

Trades
11 starter price books
Work board
Lead to Paid, 7 stages
Crew seats
Free

Product 2026

Caestro

Work starts with a Space.

A shared workspace where people and AI agents hold the same job, in the same place, under the same approvals.

Unit of work
The Space
Roster
People and agents, one list
Outbound
Held for approval

Service 2026

GeoForge

Own the ads in your ZIP code.

Local geofencing advertising sold by the ZIP code, with one business per category in each ZIP and the territory written into the agreement.

Sold by
The ZIP code
Exclusivity
One business per category
Launch
90 days, then monthly

Client software 2026 Demo data

Recruiting platform

Built for one team, who use it every day.

Sourcing, enrichment and pipeline software built for a national mortgage lender's in-house recruiting team.

Users
An in-house recruiting team
Tests
392
Agent access
Own MCP server
The recruiter queue, with candidate context and the assistant panel alongside it.

Client software 2026 Demo data

Loan officer CRM

One book per officer, and it fails closed.

A lead CRM for employed loan officers working consumer reverse-mortgage enquiries from several sources at once.

Regulated
Consumer mortgage leads
Auth
Authenticator MFA, required
Deployment
Independent of every other system
A lead record held behind a do-not-call check, with the next step and the officer it is assigned to.

Approach

Agents propose. Code enforces.
A person approves.

The boundary is in the architecture

Every system here lets AI do real work and stops it at the same line: nothing reaches a customer, and no money moves, without a person pressing the button. That is not a setting somebody could switch off on a bad Tuesday. It is where the code puts the wall.

Failing closed beats failing quietly

The loan officer CRM refuses to start against a database it does not expect. Borrowed credentials, example secrets and insecure origins stop it dead. Software that runs in a state nobody intended is worse than software that will not run.

One head, one architecture

One database to back up, one thing to deploy, background work in the same process. For teams this size, an architecture that fits in one person's head is worth more than one that would scale to a thousand users it will never have.

Nothing third-party runs here

This site serves every byte from its own origin under default-src 'self' — no external scripts, fonts, styles or trackers. The same discipline the client work is held to.

The person behind Forge

Built by Gaige.

I'm Gaige Roberson. I operate Forge Management personally — designing and building Caestro and BizForge OS, running GeoForge, and writing the platforms two teams at a national mortgage lender use every day.

Forge began operating in January 2024, from Birmingham, Alabama.

Contact

Send a message.

Ask about Caestro’s beta, GeoForge, or the work behind Forge.

Your name, reply email and message go to Forge’s inbox. Please leave out passwords, payment details and other sensitive information. Privacy information.

Prefer email? [email protected]