I build operations software because I run operations.
A K-12 transportation director in Michigan with five products of my own. Design, build, and the consequences.
Work
5 projects
JP Farm Ops (opens jackpinefarms.farm)
Storefront and back office for direct-to-customer farms. Orders, pickup events, coupons, and pop-up market requests in one place, with SMS going to the people who need it. Live at jackpinefarms.farm. A working farm business takes real orders on it.
DirectTranspo K12
Route planning for K-12 transportation departments. Deliberately manual. The director routes, the software doesn't guess. Roster import from CSV or Excel, address geocoding with a confidence check, and student data held under FERPA and state privacy agreements. Built from the input of directors, dispatchers, and drivers.
JP Calc (opens jpcalc.com)
Estimating and bid tool for residential builders. Material, labor and cost takeoffs with waste allowance, output as a client-ready proposal on the contractor's own letterhead.
BoardOS (opens boardos.co)
White-label job board platform. Operators, agencies and associations launch a branded board on their own domain, with automated job sourcing and Stripe billing built in.
LaneLogic Jobs (opens lanelogicjobs.com)
Credentialing platform for commercial transport. Carriers define the certifications a role requires, drivers are matched against what they actually hold, and DOT and MC numbers are verified before an employer appears on the board.
I run the products I build.
BoardOS is mine, end to end. That means the architecture, the interface, the vetting layer, and every decision about what ships next. I've made the calls you'll be asking me to make for you, and I've lived with the ones I got wrong.
What I do
- Design
- Interfaces for complex product surfaces like dashboards, onboarding, admin, and settings. The screens people use every day, not the ones they see once.
- Build
- Front-end implementation in React and Next.js, handed over as code your team can keep.
- Marketing sites
- Positioning, page structure, and design for sites that have to carry a technical product.
How this works
Start with a call. Thirty minutes, free, no deck. You tell me what you're building and I tell you honestly whether I'm the right person for it.
Then a fixed-scope project or a defined sprint. Fixed scope when you know what you need. A sprint when the shape is still forming and we figure it out by building. Projects start at $7,500; sprints run $6,000 a month.
Smaller than that? Still worth the call. One screen that isn't working, a flow your users keep abandoning, a second opinion on an architecture decision before you commit to it. I take short pieces of work when the fit is right.
Then monthly, if it's working. Most work doesn't end at launch. I keep going at a monthly sprint, or I hand over the code and you take it from there. Both are fine.
Who you're working with
I'm Stephanie. I run transportation operations for a school district in Michigan, and I've been building software since 2019. Five products of my own, all of them for industries I've worked in.
That's the pitch. I know what a dispatcher does at 5 a.m. and what a director does when a route breaks at 6:15, and I've watched software fail in both of those moments because whoever designed it had never been in the room. I build the other kind.
LL Tech Group is mine. When you hire it, you get me.
I take two client projects at a time. If I'm booked, I'll tell you when I open up rather than stretch your schedule to fit mine.
Tell me what you're building.
Send a few lines about the product and the timeline. I reply within a week, usually sooner.
Got it. I'll read this and reply within a week.
Prefer email? [email protected]