Custom software for businesses that work in the field

Case studies

What we mean by custom software

Off-the-shelf software is built for the average business. Custom software is built around yours: the forms your crews already fill in, the approvals your office already chases, the records an inspector or customer will ask for. We build the app that replaces the binder, the group text and the spreadsheet that only one person understands.

Most of what we build falls into three kinds:

• Operations apps that track requests, approvals and records in one flow, so nobody has to ask "who ordered this, and who said yes?"
• Employee portals that a crew actually opens every day: safety, schedules, reminders and recognition in one place.
• Compliance record apps that capture a record once, in the field, and turn it into the export a regulator or customer accepts.

Built from real projects

Every claim on this page comes from work on the shelf. Client names stay anonymous unless the client says otherwise.

An employee portal for a utility line-clearance company

Safety paperwork, payroll reminders and recognition lived in binders and group texts. The crews needed one place that worked on a phone in a bucket truck. We built the Field Crew Portal: field safety audits on checklists built on OSHA and ANSI requirements, with corrective-action workflows so every finding has an owner and a due date. A rewards system with levels, badges, streaks and seasons sits on a points ledger, so every badge and raffle drawing can be checked. Payroll and certification reminders go out by text automatically, and every message is logged.

Compliance records for a drone-spraying operator

Regulators want mix and application records for every job, and the operator was keeping them by hand. Spray Log captures each record once in the field and exports it as a clean PDF, with quotes and estimates and a map view in the same app. It has 82 unit tests and authenticated end-to-end runs in Playwright that cover the real flows, so a deploy never breaks the season.

Purchase orders without the email chains

For a field services company, we built a purchase-order workflow: requests, approvals and records in one flow, so who ordered what, and who approved it, is on the record instead of buried in email.

A live auction platform, reworked

Auction Engine started as an unsolicited UI audit of an online auction house's live bidding platform and became the engagement: interface upgrades, revenue changes, lot strategy, and an analytics center that records the baseline and every month after it, so each change can be measured.

How a custom software project runs

We follow the same four steps on every build.

1. Understand the work where it happens. We start with the people doing the job and the tools they use now, not a blank spec.
2. Build the first version you can use. A small working version comes first, so you can use it and tell us what is wrong.
3. Build with our own agent system. We build with Project Swarm, the open-source build system we created, where every change is checked and tested before it merges.
4. Hand over, support and keep improving. You get the code and the notes. We stay on to fix, support and improve it.

What we build with

The apps above are built with Next.js and TypeScript, with Supabase (a hosted Postgres database) behind them, Supabase Edge Functions and ClickSend for the crew texts, Make for connecting other tools to the purchase-order flow, and Playwright for end-to-end tests. They are widely used, well documented tools, so the code is not locked to us.

Built for the people in the field

The Field Crew Portal had to work on a phone in a bucket truck, and Spray Log had to capture records where the spraying happens. That is the brief for most of what we build: the app goes where the work is, instead of the work coming back to the office to be typed up.

Questions people ask

How much does custom software development cost?

It depends on what the software has to do, how many people use it and what it has to connect to. We do not publish a price list. We work out the scope with you first, and the first version is kept small so you can use it before deciding on more.

Do we own the code?

You get the code and the notes at hand-over.

Can you work with a business outside Arkansas?

Yes. We are in Harrison, Arkansas, and work with businesses anywhere in the US by email and phone.

Can you take over software someone else built?

Yes. Auction Engine was a live bidding platform we took over from its owner.

Will you show us a private build?

Private builds are never linked from this site. Email or call and we can arrange a demo.

Other services

• AI automation: Scheduled texts, records that fill themselves in, approvals and reports, with AI only where it earns its place.
• AI agents: Agent systems with scoped jobs, review and spend limits, built on the same tools we use to build this site.
• Websites: Fast marketing sites, from menu-first local pages to 3D and scroll-driven sites.