Field bookNº 01
Property of Buck's & Co. LLCLafayette, Louisiana
If found:buck@bucksandco.co
Software for the people who do the work. Built by someone who's done it.
the short version —
I spent twenty years in offshore medicine and operations, watching important work get held together by spreadsheets, shared folders, checklists, and somebody's memory. Buck's & Co. is where I turn those kinds of problems into practical software.
Page 1 · Why this exists
Start with the real job.
for software's sake.
Most software starts with a feature list. I'd rather start with the ugly part of the work: the workbook that became a database, the folder nobody wants to clean up, the schedule that takes too much hand editing, or the process only one person fully understands.
That is the thread through Buck's & Co. Some builds grow into products. Some stay small internal tools. The point is the same: understand how the work actually happens, preserve the useful parts, and make the brittle parts easier to live with.
- 20 yearsoffshore medicine and operations
- Focused toolssolve one useful problem before chasing ten more
- Directthe person building it is the person you talk to
Page 2 · Products
What I'm turning into products
Remedy and ComPar come from operational problems. Sproutle and Dugout came from problems I hit while building software. Each one is tagged with where it actually stands today.
Status as of September 2026
Page 3 · Free tools
Useful enough to give away.
finished tool.
Crew Change Calendar
Build common rotation schedules into a visual calendar instead of rebuilding dates by hand. It is the first tool I'm preparing for the free-tools shelf.
Page 4 · Custom operational tools
Turn the spreadsheet into the tool.
If an important process is living in Excel, a shared folder, a repeated form, a hand-built calendar, or a task somebody repeats over and over, show me how it works. I'll tell you whether a small tool or automation can give that time back.
Work order
- Requested by
- You
- The job
- The thing everybody works around instead of fixing.
- Size
- SmallMediumBigall fine
- You get
- A straight answer on whether I can help.
SignedBuck
Email Buck about a processPage 5 · How I work
Practical rules before clever features
Keep what already works
I don't start by replacing everything. I start with the piece that wastes time, breaks easily, or depends too much on one person.
Keep the data practical
Local-first where it makes sense, with useful files and exports instead of trapping the work inside a platform.
Keep a person in the loop
Automation should remove repetition, not remove judgment. Important extracted or generated information gets reviewed before it counts.
Say where it really stands
A prototype is a prototype. A pilot is a pilot. What works today and what is planned are shown separately.