Grounded Software joseph@groundedsoftware.com

Proposal No.GS-2026-049 June 3, 2026

Prepared for Flying Eagle Oilfield Services, LLC · Laredo, Texas Valid 30 days

Flying Eagle OS · Road to Production

One ticket, entered once, that bills itself and pays itself.

Flying Eagle OS is a custom system built around your paper ticket book: field tickets, customer invoicing, and weekly driver payroll, all computed from the same record. This proposal covers building it end to end and taking it live, in five milestones — each priced as a fixed fee, invoiced at the start of that milestone. No whole-project deposit, no open-ended hourly billing.

Where the return comes from plug in your own numbers

One entry,
everywhere

A ticket keyed once drives the invoice line and the pay stub. The re-keying into pay spreadsheets — and the errors that ride along with it — goes away. office hours saved / week × wage × 52

Pay that reconciles itself

Every stub is computed from the same hours that get billed, frozen at each pay run. Discrepancies between hours claimed and hours billed surface on their own instead of hiding in a spreadsheet. even 1% of annual payroll recovered

Invoice sooner, funded sooner

Tickets become a finalized, printable invoice in minutes — ready for Charter Capital the same week the work happens, not whenever the paperwork catches up. days shaved × average daily receivables

No ticket left unbilled

Gapless invoice numbering and an automatic sweep of unbilled, unpaid tickets mean a ticket structurally cannot fall out of the process — late paper carries into the next cycle on its own. 1 recovered ticket / week × your rate × 52

The milestones fixed fee · invoiced at milestone start

Core system

Field-ticket records mirroring the preprinted book — ticket numbers, gauges, hours, delay/travel/sleep. Batch quick-entry for keying a stack of tickets in one pass. Invoicing with draft → finalized → paid lifecycle and printable invoices carrying your remit-to and the Charter Capital assignment notice. Weekly payroll runs with printable per-driver stubs. Management screens for customers, leases, disposal sites, drivers, and trucks. A per-ticket audit trail of who did what, when.

Done whenA ticket entered in the system comes out the other side as an invoice line and a pay-stub line, on screen and on paper.

$10,100At start

Refinement & iteration

Your office gets hands on the working system, and I reshape it around how the work actually flows — faster entry paths, screens rearranged to match the desk, rough edges from first contact smoothed out. Scope is feedback, not a feature list: whatever daily use surfaces, within the system built in milestone 01.

Done whenYour office can run a full week's tickets and driver hours through the system start to finish without falling back to a spreadsheet.

$2,000At start

Testing & verification

Side-by-side checks of the system's arithmetic against your real records — rates, terms, invoice numbering, pay math — with every difference between how the system computes and how you actually bill and pay brought to exact parity before anything goes live.

Done whenThe system recreates one of your past invoices and one past pay week line for line, matching to the cent.

$3,500At start

Production launch

The live, secured system at your own address: staff accounts with the right permissions, your actual customers, leases, disposal sites, driver roster, rates, and fleet loaded in, and all demo data retired.

Done whenYour office signs in at the company URL and enters a real ticket.

$3,000At start

Pilot & hardening

Two to four weeks running alongside your current process through one full billing cycle. I refine the existing screens as real use surfaces rough edges and stay on call through your first real invoice and pay week.

Done whenA real customer invoice and a real pay week both reconcile against your manual process.

$3,800At start

Project total $22,400

Five milestones, invoiced one at a time — never all at once

How billing works

Each milestone is a fixed fee, invoiced in full when that milestone begins — you never pay for the whole project up front, and you never receive a surprise hourly bill. Every milestone ends at a concrete, testable done-state (listed above), and the next milestone doesn't start, or bill, until you've seen the previous one working.

New capabilities identified during the pilot — reports, statements, driver-facing views — are quoted separately as their own milestones. Ongoing support after launch is offered as a monthly arrangement, quoted at go-live.