Custom web and mobile software for service businesses and marketplaces

I build custom web and mobile software around existing business processes — including customer ordering and service requests, scheduling, job management, delivery and fulfillment, customer and staff portals, administrative tools, forms, notifications, document and media sharing, and other workflow automation.

If part of your business still depends heavily on phone calls, email, spreadsheets, paperwork, or staff manually moving information between systems, there may be an opportunity to make that process easier.

No.

You should be able to explain how your business works, what you want to improve, and what customers or employees need to be able to do.

I'll determine the appropriate technical approach and explain any decisions that affect your business.

Mostly, I need to understand the business process.

Existing forms, spreadsheets, screenshots, documents, examples of how staff currently handle the work, branding assets, and access to systems that need to be integrated can all be useful.

You do not need to prepare a technical specification before contacting me.

Before development starts, we'll agree on the project scope, milestones, deliverables, and pricing.

I generally request 25% at the beginning of the project.

Projects are then divided into clearly defined milestones. For many shorter projects this means approximately four major milestones. Projects lasting three months or longer will generally use approximately two milestones per month so progress and payments stay predictable.

Milestone payments are due when the milestone is completed and before development begins on the next milestone.

I generally use Contra.com for payments because it is easy for clients to join and offers low-fee payment options.

I generally try to provide testable software within the first two weeks.

I prefer an ongoing feedback process rather than disappearing for months and revealing the finished product at the end.

You'll be able to see and use working software early so we can identify misunderstandings, improve workflows, and make smaller adjustments while those changes are still easy to incorporate.

Small adjustments and clarifications are a normal part of the testing and feedback process, and I generally incorporate reasonable in-scope changes as development progresses.

If a change significantly expands the original requirements or introduces a new feature that wasn't part of the agreed project, we'll define the additional work as a new milestone with its own scope and budget before I begin it.

My current work primarily uses:

React, Next.js, React Native, Expo, TypeScript, Node.js, Supabase, PostgreSQL, Firebase, Swift, and SwiftUI.

I've worked with many other platforms and technologies during more than 25 years of software development, so I choose tools around the needs of the project rather than forcing every business into the same technical solution.

A basic mobile application with clear, well-defined features will commonly take approximately 4–6 weeks to develop.

More complex applications may take longer depending on the number of workflows, integrations, administrative features, or external services involved.

Mobile app review and release may require an additional 1–2 weeks, depending on Apple or Google review times and whether they request any changes.

Early mobile testing generally happens through Apple TestFlight and Google Play testing releases.

You'll be able to install the application on real phones, use it yourself, and provide feedback before anything is made publicly available through the app stores.

Depending on the project, the software may require accounts for hosting, databases, Apple or Google developer programs, email delivery, text-message delivery, payment processing, mapping, file storage, and other third-party services.

I'll explain what each account is for, why it is needed, and walk you through creating it.

Often, yes.

If an existing service provides a usable API or other integration method, I can often connect new software to services your business already depends on instead of replacing everything.

Where appropriate, yes.

I build administrative tools that allow employees to handle normal day-to-day operations themselves, such as processing customer requests, changing statuses, scheduling work, uploading documents, managing customers, and completing normal administrative tasks.

You do.

Your project's source code will be stored in a GitHub repository that you own.

I'm also happy to sign reasonable NDA, confidentiality, intellectual-property, and work-for-hire documents as required by your business.

Bugs in functionality included in the agreed project scope are covered for 30 days after launch, unless we agreed to different support terms before the project began.

If something that was included in the agreed requirements is not working correctly, I'll fix it during that period without treating it as a new feature.

The software remains yours, and there is no requirement to keep me on a monthly contract.

I'm available when you need additional features, integrations, maintenance, platform updates, workflow changes, or other improvements.

I work primarily with American companies and structure my availability so I can coordinate during normal U.S. business hours.

I'm based in both Central Arkansas and Western North Carolina, and I'm available across both Central and Eastern time zones.

I generally respond the same business day to messages received before approximately 3:00 PM Eastern Time.

Messages received later in the day will generally receive a response the following business morning.