← All work
PRODUCT DESIGN / DEVELOPMENT / COMMUNITY RELEASE

NXTDeal

A connected dealership workspace, from brand concepts to a community source handoff.

Active development concluded · Released for others to build on · October 2026

NXTDeal product presentation showing its sales workspace
Retained development imagery. Explore the complete source and current handoff notes on GitHub.
01 / THE PROJECT

From an idea
to a working exploration.

NXTDeal brought my automotive and marketing experience into a larger software project: a shared workspace for the work happening across a dealership. I explored the brand, product experience and development process, then published the source so others can take it further. My active development is complete; the software remains a work in progress.

The problem

A customer relationship crosses sales, marketing, inventory, service and finance, while the work often lives in separate tools. NXTDeal explored how those departments could share context and give people a clearer next step.

What took shape

Developed from the DealerOS codebase, the project combines a FastAPI/Python backend, a Next.js/React frontend, a dealer administration Hub and a separately developed Chrono decision-support component. The interface direction follows the work across departments, from follow-ups and customer records to operational analysis.

FastAPI / Python · Next.js / React · Dealer administration Hub · Chrono integration · Docker rehearsal stack

02 / IDENTITY CONCEPTS

A visual language for the idea.

The identity concepts combine forward-moving forms with a bright focal point, linking NXTDeal visually to Chrono. The wordmark, app icon and dark glass interface explore a consistent visual language across the product and its presentation.

Wordmark & identity direction
NXTDeal app icon concept
App icon & symbol
04 / WHAT I LEARNED

Beyond the first prompt.

NXTDeal showed me what changes when an idea becomes a system with many moving parts. I learned to turn broad product goals into smaller development cycles, make prompts specific to the task, and carry context between coding environments. Reviewing interfaces, testing behavior and documenting a handoff became as important as getting the first version to run.

Building, reviewing, repeating

These projects gave me a fuller understanding of how prompt engineering fits into development: defining the problem, breaking it into manageable changes, checking the result and refining the next instruction. That experience now informs how I approach marketing systems and creative workflows.

05 / THE HANDOFF

Take it from here.

The public repository is a community handoff snapshot, not a supported commercial service. Features and integrations vary in completeness, and the repository identifies remaining setup and validation work. Others can continue development under its published license terms.

Original software source and text documentation are MIT-licensed. Media, fonts, logos, artwork and trademarks are excluded from that software license; see the repository’s asset notice.

Source, documentation & release notes ↗
Explore Chrono ↗View my experience ↗