What is custom database development, and how is it different from off-the-shelf software?
Off-the-shelf software gives every buyer the same structure. The data model, the screens, and the reports are fixed by the vendor, and your team adapts its work to fit them. Custom database development reverses that. PCG designs the database schema, the business rules, and the screens around how your operation already works, so the software fits the process rather than the process bending to the software.1
Underneath, a PCG custom database is a standard SQL Server database with a .NET application on top. That matters for a reason beyond performance: it is a documented, widely used platform, not a proprietary format only one vendor understands. The difference buyers feel day to day is that a custom database can hold the exact fields, the exact relationships, and the exact calculations the business depends on, including the ones no packaged product has a place for.2
How do you know when your business has outgrown spreadsheets and off-the-shelf tools?
The decision rarely arrives as a single event. It shows up as a pattern of workarounds that each looked reasonable on its own. A few signs appear together in most operations that have outgrown their tools:
- A spreadsheet has quietly become the system of record for a critical function, and only one or two people know how to keep it correct.
- The same data is entered in more than one place because the systems do not talk to each other, and the copies drift apart.
- Month-end reporting is a manual assembly job rather than a report the system produces on its own.
- The packaged product cannot represent a rule your business actually runs on, so the rule lives in someone's head or in a side file.
- Adding a user, a location, or a product line makes the current setup slower or more fragile rather than simply bigger.
Any one of these is tolerable. Three or more at once is the point where the cost of the workarounds has passed the cost of building the right database. PCG covers the specific versions of this pattern in the Spreadsheet Trap, the Hidden Cost of Data Silos, and what happens when one person owns the spreadsheet the business runs on.3
Custom database, configurable platform, or off-the-shelf: which fits your business?
There is no single right answer. The question is which of three paths matches the gap between what your work requires and what a product can do out of the box.
Off-the-shelf or packaged fits when
- The process is standard for your industry and rarely bends
- The reports the product ships with answer your questions
- You can live inside the vendor's data model and limits
- Integration with your other systems is light or not needed
A custom database fits when
- Your rules, fields, or reports have no place in a packaged product
- Data lives in several disconnected systems that must agree
- You need the system to connect to the rest of the business
- You want the data and its structure to stay under your control
Between those two sits a third path. A configurable platform gives you a working system faster than a full custom build while still fitting your workflow more closely than a rigid product. FireFlight Data System is PCG's configurable platform, and for many operations it is the right first step before, or instead of, a fully custom database.
Not sure if you need a configurable platform or a full custom build?
FireFlight is PCG's configurable platform for operations, inventory, compliance, and reporting. Try it for 14 days, no obligation.
What does a custom database give you that a packaged product cannot?
The value of a custom database is not more features. It is a closer fit between the system and the business, in three places that packaged products cannot reach.
Fit to your workflow
The screens, fields, and rules match how your team already works, so people enter data once, in the place the work actually happens.
Your data, connected
The database holds one version of the truth and connects to the other systems you run, so the numbers agree instead of drifting across copies.
Rules the system enforces
Validation and business logic live inside the database, so bad data is caught at entry rather than found and corrected at month-end.
That third point carries weight beyond tidy records. Gartner reported in 2026 that poor data quality or limited data availability is one of the leading direct causes of failed AI and analytics projects, ranking alongside the skills gap.4 A business that cannot trust its own data cannot build reporting, automation, or AI on top of it. A custom database puts the integrity at the foundation, where every later decision depends on it.
Who owns the database and the data when PCG builds it?
This is the question that decides how free you are later, and the answer is specific. Your data is yours. You own and control the information the system holds, and because a PCG custom database runs on standard SQL Server, that data is readable, exportable, and portable, not trapped in a proprietary format.2
The system itself is built on widely used, documented technology, SQL Server and .NET, and delivered with the documentation a technical team needs to run and extend it. That means the business is not locked to a single vendor to keep the system alive. Any qualified .NET developer can maintain it, which is the opposite of the dependence that packaged products and departed-developer situations create.5
What does the path to a custom database look like?
PCG runs the work in four phases, each producing something the business owns whether or not the next phase proceeds. The scope and schedule of each phase depend on the specific project and are set during the diagnostic, not promised in advance.
- Discovery and data audit. PCG documents how the current process works, where the data lives today, what rules the business runs on, and what reports it must produce. The deliverable is a written map the business keeps either way.
- Schema design and prototype review. PCG designs the SQL Server schema and the primary screens, then builds a working prototype for the team to review before any production development begins. Catching a mismatch on a prototype costs an hour; catching it after build costs far more.
- Build and validation. PCG builds the .NET application against the approved schema, with the business rules enforced in the database, and validates it against real workflows and representative data before it goes live.
- Migration and cutover. Existing records move into the new database with a reconciliation that confirms what left the old system arrived intact. The legacy spreadsheets or system stay available during a verification window, so the business is never exposed to a single risky switch.
When the existing system is an old database rather than spreadsheets, the same method applies. PCG covers the specific cases in the Microsoft Access Exit Strategy and in what custom .NET development looks like for a mid-sized business.
See what a system built around your data feels like.
Start a 14-day free trial of FireFlight, PCG's configurable platform, before you decide between configuring and building custom.
Frequently Asked Questions
1 Phoenix Consultants Group, Custom Database Programming service overview. phxconsultants.com
2 Phoenix Consultants Group, Custom .NET Software Development service page. phxconsultants.com
3 Phoenix Consultants Group, Tech Wisdom: Spreadsheet Trap; Hidden Cost of Data Silos; What Happens When One Person Owns the Spreadsheet. phxconsultants.com
4 Gartner, press release: "Gartner Says AI Projects in Infrastructure and Operations Stall Ahead of Meaningful ROI Returns," citing poor data quality or limited data availability as a leading direct cause of AI project failure, April 7, 2026. gartner.com
5 Phoenix Consultants Group, Tech Wisdom: My Developer Disappeared; What Do I Do? phxconsultants.com
For environmental and engineering teams whose work orders, equipment maintenance, and job costs still live across spreadsheets, whiteboards, and email. FireFlight pulls that field work onto one operating record.
- Building operational software since 1995
- Configured around the way your operation runs
- Hosted and maintained by PCG
What is FireFlight?
FireFlight is field operations software built by Phoenix Consultants Group. It connects work orders, equipment maintenance, assets, and projects on one record, so your team can see what is running, what is down, and what is due without checking five places.
The hard way
Your operation outgrew spreadsheets a long time ago
Equipment goes down
A truck or a rig stops and nobody sees the open work order until the whole crew is backed up.
Maintenance slips
A service was due last week but lived in a sheet nobody checked, so the machine failed instead.
Jobs lose track
Project costs are scattered across files, so a job slips behind before anyone can see the numbers.
The connected way
One system that runs the site, not ten that track it
- Put the work on one record so orders, equipment, assets, and jobs stay connected on a single database.
- Stay ahead of maintenance so a service that is due or overdue shows up before the machine fails.
- See work order status as it changes so what is in progress, waiting, or behind is visible before it becomes a problem.
- Track job cost against the work so a project that is slipping is something you watch, not something you find out later.
Equipment and maintenance
Keep your equipment running, not guessing
Every asset has a record: what it is, where it sits, and what is due next. Preventive maintenance runs on a schedule the system tracks for you, so a missed service shows up before a breakdown does.
Work orders
See every work order and where it stands
Work orders live in one view, from the moment they open to the moment they close. You see what is in progress, what is waiting on parts, and what is behind, without asking three people or checking a whiteboard.
Projects
Track every project and what it costs
Each project holds its own work and costs in one place, so you know what stage a job is in and what it is running you. Contract dates and current dates sit side by side, so a project that is slipping shows up while there is still time to act.
Best fit
Built for environmental and engineering field operations
FireFlight is built for field operations that need one clear view of equipment, work orders, and jobs, instead of records scattered across separate tools.
Why PCG
Operational software is what PCG has built since 1995
- FireFlight is configured around your workflow so your team is not forced into a rigid off-the-shelf product.
- PCG hosts and maintains the platform so your team can focus on the work instead of servers, updates, and infrastructure.
- Your data stays yours and can be exported, reported, and used across your operation.
- Support is direct so you can talk to people who understand the system and the work behind it.
Questions
Common questions about FireFlight
Is FireFlight built for field operations?
FireFlight is configured per operation. For environmental, engineering, and field service firms, that means work orders, preventive maintenance, asset tracking, and project management set up around your crews and equipment. PCG builds and hosts the platform and configures the modules your operation actually uses.
How is this different from a spreadsheet?
A spreadsheet tracks what already happened. FireFlight runs the work as it happens, with every order, machine, and job reading from the same live data, so nothing falls out of sync between shifts or sites.
Who owns the data, and who runs the platform?
Your data is yours, and you can export it at any time. PCG builds, hosts, and maintains FireFlight as a service, so your team never has to manage servers or updates.
How long does it take to go live?
Timelines vary by operation and the modules involved. FireFlight is built to configure faster than a traditional custom build, and PCG runs the new system alongside your current process so nothing stops during the transition.
What does getting started look like?
You can start the 14-day FireFlight free trial and walk through the system with your own operation in mind, or book a 20-minute call to see whether your operation is a fit. There is no commitment either way.
See FireFlight running your kind of operation
Try FireFlight free for 14 days and walk through equipment, work orders, and projects with your own operation in mind, or book a 20-minute call.
Your legacy ERP is still running. But running is not the same as working. Learn how to calculate what an outdated ERP is actually costing your operation and what a realistic transition plan looks like.
Last updated: May 2026 Phoenix Consultants Group | Custom Software ROI Framework for Small and Mid-Sized Businesses You measure ROI on custom software by capturing a baseline before go-live, picking three or four workflows to track, and running structured reviews at 3, 6, and 12 months. The answer is not one number. It is a […]
What was breaking in soil remediation tracking before this project?
The client was managing an active Superfund cleanup under EPA oversight. Federally supervised environmental remediation comes with reporting obligations that the project sponsor cannot defer or simplify. Volumes of contaminated soil removed must be documented at the cubic yard level. Source locations and destination disposal sites must be traceable for every load. Contamination testing results must link back to the specific soil they describe. And the projection of how much soil remains to be treated, which determines the timeline and cost trajectory of the entire cleanup, must be defensible to the regulator.
Spreadsheets do not survive that scrutiny. They lose data integrity as multiple people edit them. They cannot enforce relationships between source location, destination, and testing record. They produce projections that no one can audit because the formulas drift over time. For a Superfund site under active EPA supervision, that is not an inconvenience. It is a regulatory exposure that grows with every reporting cycle.
For a Superfund cleanup, the consequences of weak tracking infrastructure compound over time. EPA does not forget reporting gaps. Timeline projections that turn out to be inaccurate get challenged in subsequent reviews. Funding decisions for the remaining cleanup phases depend on the credibility of the data presented. A tracking system that cannot defend its own outputs creates problems that outlive the cleanup itself.
What did PCG actually build for the EPA Superfund tracking environment?
PCG developed a database-backed tracking system designed specifically for federally supervised soil remediation. The architecture handled the complete data chain from contaminated source through testing through disposal destination, with a forward projection engine that produced defensible estimates of remaining work. Each component was built so that the data trail required by EPA auditors was captured at the moment work happened, not reconstructed afterward.
Every cubic yard of contaminated soil removed from the site was logged against its source location within the cleanup area. The system tracked extraction sequences, soil type, and the date and time of each removal. Source data became the anchor that every subsequent record linked back to.
Each load of removed soil was tracked from source to destination. Disposal site records included the receiving facility, transport documentation, and chain-of-custody. EPA reporting requires this trail. The system captured it as a structured record rather than a paper manifest reconstructed at the end of each reporting period.
Testing results from soil samples were linked directly to the specific soil they characterized. Test method, lab, results by analyte, and date were captured against each source location. When a question arose about the contamination profile of soil sent to a specific disposal facility, the answer was a query rather than a manual file search.
The system included a calculation engine that projected forward to estimate remaining soil quantities still requiring treatment. Inputs included treated volumes, contamination boundaries, treatment effectiveness, and remediation rates. The engine produced timeline and cost projections that were defensible to EPA because the calculations were transparent and the underlying data was queryable.
The system gave the client real-time visibility into project timeline, cost trajectory, and regulatory progress against the EPA-approved cleanup plan. Quantities removed, quantities remaining, projected completion, and costs to date were available without manual rollup from spreadsheets. EPA reporting cycles became data extracts from the live system.
Superfund sites fail their tracking obligations in a specific way. The site team usually has the data. They just cannot produce it in the form EPA requires within the timeline EPA expects. A tracking system that captures data at the moment of work and structures it for the format regulators ask for changes the equation. The data was always there. The infrastructure to surface it was not.
The forward projection engine was the part that created the most strategic value, beyond the regulatory reporting. A project sponsor who can produce a defensible estimate of remaining cleanup work has a different conversation with EPA, with funders, and with internal stakeholders than a project sponsor who is producing best-guess timelines from spreadsheets. The number itself is less important than the auditability of how the number was produced.
What changed after the system went into production?
The most immediate change was that EPA reporting cycles stopped being reconstruction projects. The data trail from source soil through testing through disposal destination was already captured and structured. Reports became data extracts. The team's effort moved from assembling reports to running the cleanup.
| Outcome | Result | How it was achieved |
|---|---|---|
| EPA reporting timeline | Data extracts, not reconstructions | Source-to-destination chain captured at the moment of work, structured for regulator format |
| Forward projection of remaining work | Defensible to regulator | Custom calculation engine with transparent inputs and queryable underlying data |
| Source-to-disposal chain of custody | Continuous and complete | Every load tracked from source location through destination disposal facility |
| Contamination testing traceability | Linked at the source-record level | Testing results attached directly to the soil they characterized, by source and date |
| Project timeline visibility | Real-time | Treated volumes, remaining volumes, and projected completion available on demand |
| Cost trajectory tracking | Tied to actual cleanup data | Costs attributed to source locations and treatment phases as work progressed |
The strategic value of the system extended beyond EPA reporting itself. Real-time projection of remaining cleanup work changed the client's ability to manage the project against budget and schedule. Decisions that had previously waited for the next reporting cycle could be made on current data. Funding conversations that had been based on best-guess timelines became conversations grounded in defensible projections.
What capabilities does this kind of system provide for federally supervised environmental cleanup?
The infrastructure built for this Superfund site addresses a problem class that appears across every environmental remediation project under federal or state regulatory oversight. The capabilities below apply to CERCLA Superfund work, RCRA corrective action, state-led brownfield cleanups, voluntary cleanup programs, and any operation where soil, groundwater, or other contamination is being tracked from contaminated source through treatment or disposal.
Every cubic yard of contaminated material tracked from source location through transport through destination disposal facility. The chain that EPA and state regulators require is captured automatically at each handoff rather than reconstructed at the end of reporting cycles.
A calculation engine that estimates remaining cleanup work based on transparent inputs and queryable underlying data. Project sponsors can produce timeline and cost projections that hold up to regulator review and stakeholder scrutiny.
Contamination testing results connected directly to the specific source location, sample, and material they describe. When a question arises about the contamination profile of material sent to a specific facility, the answer is a query against linked records, not a manual file search.
Treated volumes, remaining volumes, projected completion dates, and cost trajectory available on demand against the EPA-approved cleanup plan. Project decisions stop waiting for the next reporting cycle to be made on current data.
Technology stack
| Component | Technology |
|---|---|
| Database layer | Relational database with enforced source-destination-testing relationships |
| Calculation engine | Custom forward projection logic with transparent input parameters |
| Data capture | Spreadsheet and database integration for field data entry |
| Chain of custody | Source location, transport, and destination logged as linked records |
| Testing integration | Lab results linked at the source-record level by sample, method, and date |
| Reporting layer | EPA-format data extracts produced from live system queries |
| Compliance framework | CERCLA / Superfund supervision with EPA reporting alignment |
Does this apply if your cleanup is smaller than a full Superfund site?
The architecture scales down as well as up. State-led brownfield cleanups, voluntary cleanup programs, RCRA corrective action sites, and private remediation under regulatory oversight all face the same core problems as a Superfund site: source-to-destination chain of custody, testing data linked to physical material, defensible forward projections, and reporting that aligns with regulator format. The engineering decisions on this project transfer directly to cleanups an order of magnitude smaller.
What makes this project transferable is not the regulatory framework. It is the problem class. Any environmental cleanup where contaminated material moves from source through testing through disposal, under any oversight regime, is carrying the same data integrity risk this Superfund site was carrying before the system went live. The risk accumulates invisibly until a regulator asks a question the data cannot answer in the form required.
PCG has built environmental compliance and remediation infrastructure since 1995. The work documented here is one of more than 500 production applications PCG has delivered, with environmental and regulatory compliance representing approximately one-third of that volume across 31 years.
Frequently asked questions about Superfund and environmental remediation tracking systems
Allison has been building custom software since the early 1980s, including work as a data analyst for the U.S. Air Force before founding PCG in 1995. The Superfund remediation tracking documented here is one of more than 500 custom applications PCG has delivered, with environmental and regulatory compliance representing approximately one-third of that volume across 31 years. Her direct involvement in every project is not a policy. It is how PCG operates. When you call, she answers.
Project details documented with client permission. Specific identifying details about the Superfund site have been generalized. System capabilities and architecture reflect the actual production deployment.
PCG founded 1995. Allison Woolbert's personal experience in software development predates PCG's founding.
There is a specific kind of message that stops a leader cold.“Hey, do you have a few minutes today? I’ve got some news.”You already know what comes next. Your developer, the one whose name comes up every time someone says “we should ask before touching that,” is leaving.New offer. Burnout. Career change. The reason does […]
Custom .NET Software &
Full-Stack Data Solutions
Phoenix Consultants Group designs, builds, and rescues custom software for industrial, environmental, and operational organizations. Since 1995, the firm has delivered more than 500 applications across fleet management, compliance tracking, healthcare staffing, public safety, and legacy system migration. When a business-critical system fails and the original developer is no longer available, PCG provides the technical resolution.
- 500+ Applications Delivered
- 3 Decades in Operation
1995
Year of Founding
F500
Project Experience
30+
Year in Business
45+
Industries Served
Building Custom,
Data-Driven Applications That Power Business
We are a custom software development firm specializing in legacy system migration, compliance software, and full-stack .NET development for industrial and operational organizations. Founded in 1995, we have delivered more than 500 production applications. Our engineers work directly on every engagement, and all technical inquiries are handled by the engineer assigned to the project.
Last updated: April 2026
Core Development and Migration Services
Custom .NET Software Development
PCG develops production software on C# .NET Core, ASP.NET Core, Razor Pages, and SQL Server for organizations whose operational requirements exceed the capabilities of available commercial products. Completed systems have included fleet management platforms, physician credentialing and payroll systems, compliance tracking applications, and public safety dispatch software. Clients retain full ownership of their data, with complete documentation.
Environmental and Industrial Compliance Software
Compliance software has represented approximately one-third of PCG's three-decade project volume: waste manifests, air permits, EPA Title V, remediation documentation, and OSHA record keeping. FireFlight Data System is a modular platform developed and maintained exclusively by PCG for environmental compliance and industrial operations, delivering that same depth of domain experience in a fully hosted, directly supported system.
Legacy System Migration and Application Rescue
PCG migrates Access databases, VB6 applications, FoxPro systems, legacy ASP applications, and Excel-based operational systems to current .NET Core architecture. Business logic, data integrity, and process workflows are preserved through the migration. Existing documentation is not a prerequisite for initiating an engagement.
PCG performs technical reconstruction where source documentation is absent.
Experienced Database Administrators and Software Engineers Since 1983
At Phoenix Consultants Group, our database administrators have been developing and delivering data collection and data management applications since 1983. We have the depth of experience required to write software that meets and exceeds client requirements, with extensive work in database synchronization, multi-source data collection, and the architecture of compact, high-performance database systems.
We maintain active expertise in both current and legacy programming environments, enabling us to migrate, maintain, and modernize systems regardless of the platform on which they were originally built
Programming Expertise in Both Modern and Legacy Languages
We have maintained current expertise across both modern development frameworks and legacy languages. This dual capability is the technical foundation for our migration work: our engineers understand both the platform a system was built on and the platform it is being migrated toward.
- Visual Basic, Visual Basic for Applications, SQL Server, Microsoft Access & Excel, ASP, C#.Net, Visual Basic.NET, Razor.NET, Core.NET, ASP.NET.
- MS SQL Server, OLEDB, ADO, ODBC, MS Access, MySQL
- OLE/ActiveX, COM/DCOM/COM+
- DOS, dBase, FoxPro, Paradox, Alpha, RM Cobol
Let's Start Your Project!
Real Systems. Measurable Outcomes.
Explore measurable results from custom software built for complex operations, compliance, and long-term reliability.
Technical Situations That Typically Precede an Engagement With Us
A production system has no surviving documentation and the original developer is no longer available.
We have performed technical reconstruction and migration on production systems accumulated over 10 to 20 years of development, in cases where no documentation, design specifications, or original developer access existed. The completeness of documentation at project initiation does not determine whether a successful migration is achievable.
A Microsoft Access database is generating errors that internal staff cannot resolve.
We have maintained and migrated Microsoft Access systems across all versions of the platform since its initial release. Data corruption, version incompatibility, 32-bit architectural constraints under Windows 10 and 11, and performance degradation under scaled data volume are recurring issues with established resolution paths at PCG.
Compliance requirements are specific enough that no available commercial EHS platform provides an adequate fit.
Environmental consulting firms, industrial EHS departments, and field inspection organizations operating under agency-specific regulatory frameworks frequently encounter this gap. We have built compliance software across all three contexts: FireFlight Data System provides natural language query capability against live operational and compliance data.
A critical operational process is managed within a spreadsheet that represents an institutional single point of failure.
When the individual with working knowledge of a complex operational spreadsheet departs, the organization loses both the tool’s functionality and the institutional knowledge embedded in its logic. We convert these systems to documented, maintainable applications before that dependency becomes an operational crisis.
Some Industries
That We Serve
Emergency Services
Engineering
Environmental Safety
Fortune 500
Industrial Safety
Industry
Information Technologies
Inventory Management
Manufacturing Software
Non Profit Services
Oil & Gas
Regulation Compliance
Retail
Small Business
Transportation
FireFlight Data System:
A Modular Platform Developed and Maintained Exclusively by PCG
- Waste manifest tracking and regulatory deadline management
- Multi-site air permit monitoring and exceedance alerting
- Remediation milestone documentation and audit trail management
- EPA and state DEP compliance record management
- Field inspection data capture and regulatory report generation
- PCG-hosted infrastructure with direct engineering support
Can you just ask your operation a question?
Yes. FireFlight, the operational platform PCG builds and maintains, lets you query your live data in plain English. You do not build a report or export a spreadsheet. You ask, and it returns the matching records, ready to export.
Answers from your live data, in plain English
No SQL, no report builder. It is built into every FireFlight deployment PCG stands up.
Every answer comes with Show SQL, CSV, and PDF export on the result.
