The workspaces behind the business. Custom operations software, admin dashboards, and connected public websites.
Products that give people tools to create: from brand imagery to playable game worlds.
Products built around a particular world of work. Includes platforms I build or participate in as a product partner.
Public experiences with a clear identity, a useful journey, and a next step.
Legacy CRM Replacement
An old CRM can hold years of valuable customer history and still make every new job harder than it should be. I help businesses plan and build its replacement, carrying forward the records and operating rules that matter while removing the limits of the old system.
Jacksonville based. Serving Florida and remote clients.
Start a conversationSound familiar?
What the work covers
01
Inventory the records, reports, permissions, and exceptions your team depends on. Some of the most important requirements live in a spreadsheet next to the CRM or in the habits of an experienced employee.
02
Review exports, duplicates, field mappings, and record relationships. Agree on what moves, what stays available as history, and how the team will check the migrated information.
03
Build the quoting flow, catalog, branch access, and field screens the business needs now. A replacement should make the work easier, with familiar business logic where it still serves the team.
04
Choose a first workflow or group of users, verify it with real examples, and plan training and cutover steps. The pace depends on dependencies, data quality, and how the company keeps working during the move.
From the work
Illustrative concept with fictional data; not the client’s actual interface.
My largest custom CRM build to date, developed in collaboration with a confidential client. The illustration keeps the working system private.
Read the case studyHow we work together
Walk through a real job, the tools involved, and the points where work slows down.
Decide what to keep, connect, or build, with priorities and costs agreed before implementation.
Introduce the system in stages, learn from the people using it, and plan continued development.
Before we start
I first need to inspect its export options, database access, and data quality. That determines the migration approach and any limitations. I do not promise a complete transfer before reviewing the source.
Possibly. If an existing product fits the workflow and migration needs, it belongs in the comparison. Custom development makes sense when the business requirements justify owning a system built around them.
We plan the transition around your operation. A staged rollout is often useful, but some records and workflows need to move together. Diagnosis establishes those dependencies before a cutover is scheduled.
Based in Jacksonville. Working with businesses across Florida and clients from New York to Florida.
Have something in mind?
A website with a point of view. Software that makes the day easier. Tell me what you’re working on.
Start a conversation
