The problem wasn't abstract.

Local government project management doesn't look like what the enterprise software vendors build for. There's no dedicated PMO. There's no team of certified project managers. There's a department head who got handed a capital project, a vendor who knows the contract better than you do, and a council that needs answers at the next meeting.

The tools that exist were built for federal contractors, construction firms, or enterprise IT departments. They're priced accordingly — setup fees that exceed an entire year's IT budget, annual subscriptions that compound, and implementations that require consultants to configure. Small cities and counties either improvise with spreadsheets or go without governance entirely.

"I built PGP because I needed it. When I looked at what was available for entities our size, the options were a spreadsheet or a six-figure contract. Neither was acceptable."

PGP started as an internal tool — a structured way to bring PMBOK discipline to government projects without requiring every project manager to hold a PMP certification. The Teach Me panels exist because the people running these projects are often department heads, engineers, or administrators who are excellent at their jobs but were never trained in formal project governance. The software needed to teach while it managed.

The vendor accountability layer came from watching the same pattern repeat: a vendor submits an invoice, no one can locate the original scope document, and the dispute costs more time than the invoice was worth. PGP tracks commitments, submittals, RFIs, and transmittals because that documentation trail is where disputes get resolved — or avoided entirely.

The pricing model — $1.25 per capita — came from a simple question: what would a local government entity actually be able to get through procurement? The answer was a number tied to something real, predictable, and defensible in a budget presentation. One-time, not recurring, because government budgets are annual and a perpetual obligation is a political liability.

Eolithic Governance Systems LLC was formed to take this from an internal tool to a commercial product — built on personal time, with no county resources, and disclosed proactively to the appropriate county officials before any commercial activity began.

Founder Background

Role

Government Project Manager — active full-time government employee managing real projects with real vendors and real council accountability

Industry Membership

GMIS International — representing county in the government management information systems professional network

Methodology

PMBOK v6 — the framework PGP is built around, applied to actual government capital projects and vendor contracts

Development

Built on personal time. No government resources used. Proactively disclosed to county procurement before any commercial activity.

Company Structure

Eolithic Governance Systems LLC — single-member LLC, no outside investors, no board, no sales quota driving feature decisions

Why Eolithic?

The Eolithic period is the earliest phase of human tool use — the moment when humans first began shaping stone into instruments that could do work that bare hands couldn't. Crude tools. Effective tools. Tools that changed what was possible.

The logo is deliberately blunt about this: stone tools smashing a Gantt chart. Government project management has been done with the wrong instruments for too long — either primitive improvisation or enterprise software that doesn't fit. PGP is the right tool for the actual job.

The .US domain is intentional. This software is built for US local government entities. The domain makes that plain without a sentence of explanation.

Eolithic

/ ˌiː.əˈlɪθ.ɪk / — adjective


Origin

From Greek eos (dawn) + lithos (stone). Relating to the earliest period of human tool use, preceding the Paleolithic.

As used by EGS

The moment when the right tool changes what's possible. Applied here to project governance: structuring what was previously improvised, documenting what was previously disputed, governing what was previously guessed at.

The name is unusual on purpose. Government buyers remember it. And it says something about the philosophy — primitive in the best sense. Direct. Effective. Built for work.

A few things we won't compromise on.

01
No Feature Creep

PGP v3.0 is feature-complete. It ships when it's ready, not when a demo needs something new. Future versions are purchased separately — you're not funding a roadmap that may never arrive.

02
Honest Pricing

$1.25 per capita. Published. The same for every entity. No tiered enterprise pricing that requires a sales call to discover. No introductory rates that reset at renewal.

03
No Vendor Lock-In

Your data lives on your hardware in formats you control. If EGS ceased to exist tomorrow, your deployment keeps running. That's what perpetual licensing is supposed to mean.

04
Controlled Trials

Trials are granted, not downloaded. Not because access is withheld — because a 30-day trial is only useful if you're set up to evaluate it. We'd rather spend that time making sure the fit is real.

05
Sequence Over Speed

One product ships before the next one starts. UPMP doesn't get built until PGP generates revenue. The AI backbone doesn't get built until there's a foundation to put it on. Deliberate sequencing beats scattered ambition.

06
Government-First Design

Every decision — pricing model, deployment method, feature priority, licensing terms — is made with local government procurement realities in mind. This is not enterprise software adapted down. It's built from the right starting point.

Conflict of interest — disclosed, managed, documented.

The founder of EGS is a current government employee and GMIS member representing their county. PGP is software that could be sold to that county. That creates a potential conflict of interest, and it has been handled directly — not avoided, not minimized.

Government buyers in particular need to know that any transaction with EGS will be clean. The steps taken to ensure that are documented below.

The goal is simple: when EGS eventually approaches the county as a vendor, it will be as an outside vendor with an established price schedule and an arms-length commercial track record — not as an employee pitching their own software through the back door.

1

Proactive Disclosure

Disclosed to county procurement officer before any commercial activity. Stated clearly: developed by EGS LLC on personal time, no county resources used. Procurement officer was given beta access for awareness.

2

Separate Communications

All EGS activity uses eolithic.us email exclusively. County email is never used for EGS business. The two identities are never mixed in the same meeting or correspondence.

3

External Sales First

EGS will not approach the county as a prospective customer until arms-length transactions with other entities have established a published market price. The county gets the same rate as everyone else — no more, no less.

4

Full Recusal

The founder will recuse completely from any county evaluation, recommendation, or procurement decision involving PGP. That decision belongs to county procurement, not to the person who built the software.

Work With EGS

Straight talk. Straight pricing.
Software that does the job.

If you manage projects for a local government entity and you're tired of improvising governance with spreadsheets — or tired of enterprise pricing that wasn't built for your budget — let's have a direct conversation.