Custom business software for Sarasota.

Turn a process held together by email and spreadsheets into a usable application. I build client workflows, internal tools, and integrations around the way your team works.

Based in Savannah, Georgia. Working remotely with Sarasota teams.

A practical fit for Sarasota.

Sarasota County identifies financial and professional services, technology, and corporate headquarters among its target industries. For these teams, a practical starting point is often the handoff between a client request and the people responsible for completing it.

Sarasota County EDC: target industries

Make the next handoff clearer.

Possible projects to scope together.

A client portal

Collect requests, show progress, and keep approved documents in one place. Start with the status questions clients ask repeatedly and who should be able to see each answer.

A document review assistant

Help staff locate source material or prepare a draft from approved documents. Include source references and human review; the assistant should not make professional decisions on its own.

An intake and approval workflow

Route a new request to the right person, record a decision, and show what is waiting. Decide which information is required and who owns the next step before automating it.

Stable Manager Pro

Stable Manager Pro website for lessons, payments, reminders, and rider progress

Stable Manager Pro combines recurring operational tasks in one application. My work covered feature scope, user experience, AI-assisted implementation, and release testing. Its scheduling and payment workflows show how I approach connected business software; it is not presented as a Sarasota engagement.

Explore the project

One developer. A clear remote process.

15+ years in software and frontend engineering. AI tools accelerate implementation; product decisions, architecture, review, testing, and delivery remain my responsibility.

Define the work

We agree on the users, scope, cost, timing, and what an accepted delivery includes.

Review working software

Video calls, written decisions, and testable releases keep your team involved. We share the same Eastern time zone.

Plan the handoff

Source access, deployment notes, known limitations, and support responsibilities are agreed as part of the scope.

Before we start.

Should we buy a tool instead of building one?

Possibly. We first check whether configuring or connecting existing software solves the problem. Custom development should address a real gap, not duplicate a tool your team can already use.

Can you work with confidential client documents?

We agree on approved systems, access, retention, and whether an AI service may process the data. Use anonymized examples for the initial conversation rather than sending confidential files.

Can you train staff to use the new workflow?

Yes. Handoff documentation and a practical walkthrough can be included in the scope. Broader ChatGPT or Claude training is available separately.

Need help using AI rather than building software? Explore remote team training.

Bring one problem to the call.

Bring an anonymized example of a request, document, or spreadsheet and walk me through the current handoffs. Include the exceptions and permissions, not just the happy path.