Services
Software, websites, and apps, built for the way you actually work.
Most engagements start with one problem: a spreadsheet that outgrew itself, a site nobody can edit, a process that lives in someone’s inbox. We fix that first, then stay on for what comes next.
Software you run on
The systems your team touches every day: where work lives, how information gets in, how decisions get made, and how the numbers come out the other end.
Internal tools
Jobs, records, queues, and assignments built around the process your team actually runs.
Data collection workflows
Intake, inspections, waivers, and field entry captured once and validated at the point of entry.
Approvals and routing
Requests sent to the right person, escalated when they stall, with a record of who decided what and when.
Reporting and dashboards
Numbers drawn from the work, rather than rebuilt by hand every month.
Integrations
Connections between ERP, accounting, CRM, scheduling, and payment systems so a record is entered once.
Client and member portals
A place for people to submit information, check status, and retrieve their documents.
the master spreadsheet, the paper form, the email chain, and the monthly report rebuilt from four exports.
Websites
Marketing and organization sites that load fast, read well on a phone, and work for people using a keyboard or screen reader. Your team can update pages, posts, and events without calling a developer.
Where it helps, the site connects to the systems behind it. A contact form lands in a queue instead of one person’s inbox, a registration writes straight to your member records, and an event page pulls from the same calendar your staff uses.
the site nobody can edit, the slow page builder, and the contact form disappearing into an inbox.
Mobile and tablet apps
Native apps for iOS and Android when a browser is not enough: a camera in the field, work without a connection, notifications, or a tablet at a station on the floor.
The app uses your existing sign-in and data, so people do not need a second set of accounts. Work done offline syncs back to your systems when connected.
the consumer app bent into a workaround, or the laptop carried around the floor.
Modernization
An application that works but is expensive to host, slow, or unpleasant to use, rebuilt on current foundations. We retain the data, rules, and habits that make it useful, while changing what makes it hard to run.
the system everyone is afraid to touch.
Ongoing partnership
Software keeps changing after launch: fixes, additions, new reports, and the next tool. We stay on for that work, with a monthly arrangement scoped to what that month needs.
A quiet month might be hosting and care; another might be a full feature. Scope and price are agreed before work starts. There is no hourly meter: you know the work before it begins and can see the outcomes.
the one-off project handoff and the developer you cannot reach afterward.
In everything we build
Accessibility, exportable data, and documentation belong in the foundations, with role-based permissions and audit trails where the work calls for them. People see and change what their role allows, and important changes leave a record. These are part of building something dependable, appropriate to what is being built.
You own the code from the first commit. The system should be something you can keep, understand, and hand to another developer when you need to.
How an engagement runs →Start with one problem
Tell me what needs to work better. I will give you an honest recommendation about whether software, a website, or an app would help, what the first version should do, and what it would take.