Building a platform that covers scheduling, customer records, communication, and appointment booking means designing across very different use cases. The risk is that each use case starts pulling in its own direction and the product ends up feeling fragmented.

We established a consistent way to use components early and applied it at two levels.

1/ At the page level, consistent text sizes and layout logic.

2/ At the component level, the interaction patterns show whether you are filtering technicians, service types, or job durations.

The result is a system where you don't need many text sizes, components, or colors because everything follows a coherent logic.

The filter panel is one example of that direction.

Automated a manual Google Sheets → Slack workflow to eliminate repetitive data entry and give the team instant notifications.

Previously, new data had to be manually checked, processed, and shared across the team — slow and easy to miss. I built a Make.com scenario that:

Watches Google Sheets for new/updated rows

Processes and routes the data through a router based on conditions

Creates corresponding Trello cards for task tracking

Logs processed records back to Google Sheets

Sends real-time Slack notifications so the team is instantly updated

Result: What used to be manual checking and updating is now fully automated — saving hours weekly and removing room for human error.

Tools: Make.com, Google Sheets, Trello, Slack

wow love this