The Deliverable, The Revision, and The Invoice — One Record
Custom CRM and practice management software for civil engineering firms — project exchange with contractors, deliverable tracking, drawing revision control, and phase-based billing.
Sound
Familiar?
Common problems we solve for civil engineering businesses.
Your drawings went out by email. Now prove which revision they built from.
→A project exchange portal where every issued set is versioned, every download is logged against a named recipient, and the current set is unambiguous. When a revision question comes up eighteen months later, the answer is a query rather than an email archaeology exercise.
Deliverable status lives in one project manager's head
→A deliverable register per project — scope, committed date, reviewer, current status, and what it is waiting on — visible to the whole practice rather than reconstructed in a Monday meeting.
Revision control depends on a filename convention people forget
→Revision history attached to the drawing itself, not to what somebody typed after the underscore. Superseded sets are marked superseded and stop being served as current.
Billing is tied to phase completion, but phase completion is tracked somewhere else
→Phases carry their own percentage-complete and their own billing trigger. When a phase closes, the invoice is generated from the same record that says it closed — not re-derived from a spreadsheet at month-end.
Sealed documents need a record trail a shared drive cannot produce
→An auditable chain for regulated deliverables: who prepared it, who reviewed it, what revision was sealed, when it was issued, and to whom. Built to satisfy the documentation expectations that come with practicing engineering in Texas.
Survey data, design files, and correspondence live in three unconnected places
→One project record holding survey deliverables, design files, submittals, and the correspondence that explains them — so context does not disappear when a project manager changes.
What We Build
Custom software designed specifically for civil engineering operations.
Project Exchange Portal
A controlled handoff to contractors and owners. Versioned issue sets, named recipients, download logging, and an unambiguous current set — so a revision dispute is answered from records, not memory.
Deliverable Tracking
A register per project: scope, committed date, reviewer, status, and blocking item. Practice-wide visibility instead of a status that only one person can report on.
Drawing Revision Control
Revision history bound to the document rather than the filename. Superseded sets are marked and withdrawn from circulation automatically.
Phase-Based Billing
Percentage-complete and billing triggers on the phase itself. Closing a phase produces the invoice from the same record — no month-end reconciliation between two systems.
Sealing & Regulatory Records
Preparer, reviewer, sealed revision, issue date, and recipient captured as an auditable chain for every regulated deliverable — the record trail a shared drive cannot produce.
Survey & Design File Management
Survey deliverables, design files, submittals, and correspondence on one project record, so context survives a change of project manager.
What civil engineering actually measures
Quantities for the engineer's opinion of probable cost, and the pay item schedule contractors will bid against — earthwork volumes, pipe by size and material, structures, pavement sections, and erosion control.
By hand
The quantity schedule is rebuilt for each design revision, and the version a contractor bid is not always the version that was issued. When a bid comes in far off the estimate, working out whether the design changed or the contractor read it differently means reconstructing both.
With AI takeoff
Quantities are computed from the design surfaces and alignments and tied to the revision they came from. When the design changes, the schedule regenerates and the delta is visible — so an estimate and the set it was based on can never quietly diverge.
Civil Engineering software, answered directly
Is this a CRM?
Yes. Aeopic builds custom CRM software for civil engineering businesses — contacts, pipeline, scheduling, activity history, and reporting are all part of it. The difference is what sits at the centre of the record: your deliverable, not a generic "deal". Project exchange portal, Deliverable tracking, and Drawing revision control run inside the same system rather than in three separate tools that don't talk to each other.
What does an AI operating system actually do?
An AI-integrated operating system is a custom CRM with your operations built into it and an AI layer that can read all of it. For civil engineering work, that means the system tracks which revision each contractor actually received, flags a deliverable approaching its committed date, and assembles the correspondence record behind a sealed document. The AI is not a chatbot bolted onto the side — it has access to the same deliverables, documents, and history your team does, and every action it takes is reviewable.
How is this different from a generic project-management tool with a document folder?
Off-the-shelf software asks you to describe civil engineering work in its vocabulary, so you end up with custom fields standing in for deliverables and a spreadsheet holding whatever wouldn't fit — which is how you get a revision dispute you cannot settle from your own records. A custom platform uses your vocabulary from the start. You also stop paying per seat, and adding a capability is a change to software you own rather than another subscription.
Do I own the code?
Yes. You own the source code, the database, and the deployment. There is no per-seat license, no vendor who can raise your rate, and no feature that can be sunset out from under you. If you stop working with Aeopic, your deliverables and the system that manages them keep running, and any competent developer can maintain the codebase.
Stop Reconstructing What Your Own Records Should Already Say
Let's scope a practice platform where the deliverable, the revision it was issued at, and the invoice for that phase live in one place. Texas-based, and built for how engineering practices actually run.
No obligation · Response within 24 hours · Full code ownership