<— back
Crane Sales Process
Process automation for Home — a crane sales company
This tool visualizes and optimizes the crane sales process for Home. Built through a collaborative process of interviewing stakeholders, rapid prototyping with AI, and iterating until the core workflow emerged. The interactive process flow maps every step from initial customer contact through final delivery, making the entire sales pipeline transparent and actionable.
The Creative Process
Every project follows a deliberate process — from understanding the problem to delivering a polished tool. Here's how this one came together:
1. Interview with the company
Sat down with the team at Home to understand their current sales process, pain points, and what success looks like. This is where domain knowledge enters the picture.
2. Ideation through vibe coding
Using AI-assisted prototyping to rapidly explore ideas. Instead of wireframes and mockups, we go straight to working code — testing concepts in real time.
3. A prototype with way more than needed
The first prototype is intentionally over-built. More features, more screens, more possibilities than the final product will ever need. This is the raw material.
4. Boiling down to the core
Strip away everything that isn't essential. Remove features, simplify flows, and find the core of what this tool actually needs to do. Less is more.
5. Adding back what matters
With the core identified, selectively add back features that directly address the needs uncovered in the interview. Every addition must earn its place.
6. From prototype to user stories
The refined prototype becomes a living specification. Instead of abstract requirements documents, we have a working tool that communicates exactly what needs to be built.
7. Applying the company identity
The final step: scrape Home's brand identity and website, then apply their colors, typography, and visual language to the tool. The result feels native to their brand from day one.
Why not just use Figma?
Traditional design tools produce static mockups that look like the final product but don't behave like it. This approach is different: every prototype is functional code from the start. Stakeholders don't review screenshots — they click through a real tool, with real data, and give feedback on actual behavior. The prototype isn't a promise of what will be built. It is what's being built. This collapses the gap between design and development, eliminates handoff friction, and means the team can validate ideas in hours instead of weeks.