WikiPro Web

Lawn care companies, cleaning services, legal firms, and retail operations all run on the same three things: staying in touch with customers, protecting their reputation, and winning repeat business. WikiPro is the cloud platform they do that on. It replaces six to eight separate tools with real-time SMS and team chat, calendar and appointment scheduling, review monitoring across Facebook, Google, Yelp, and Amazon, automated surveys with NPS tracking, payment and transaction management, a full CRM, marketing automation with campaigns and drip flows, and reporting dashboards. Businesses onboard their teams into an organizational model covering staff, departments, signatures, and role-based access, then reach their customers through SMS, scheduled messages, and templated workflows.

This project was a full platform redesign spanning nine core modules: Chat, Calendars, Reviews, Surveys, Payments, Customer Management, Marketing, Reports, and Settings. WikiPro had reached that scale the way most feature-rich platforms do, one module at a time, starting as a simple messaging tool and accumulating reviews, surveys, payments, marketing, and CRM along the way. Each addition solved a real need. Together, they had stopped feeling like one product.

WikiPro carried the accumulated friction of a platform that had grown without a cohesive design strategy. Each module had its own visual language, navigation patterns, and interaction models, so the experience fragmented as the product expanded, leaving a steep learning curve for new users and daily cognitive overhead for everyone else. Six problems shaped the work:

The approach was a module-by-module overhaul unified under the Align UI design system, so visual consistency and scalable component architecture came from the foundation rather than being negotiated screen by screen. Every module was rebuilt against that shared vocabulary, and where the platform needed patterns Align UI did not cover, I extended the system with a local component library rather than letting one-off UI creep back in.

On that foundation I reorganized the platform around the work service businesses actually do. Chat became the communication nerve center with a three-panel layout. Calendars, Reviews, Surveys, Payments, Customer Management, Marketing, and Reports each got an information architecture matched to their data: overview dashboards where users need a read on performance, sortable tables where they need to operate on records, and sub-navigation that adds depth without cluttering the top level. Settings moved to a two-panel structure that made a long list of configuration areas navigable. Three cross-cutting layers ran through all of it: light and dark mode variants for every module, interactive icon hover states with contextual tooltips on the global sidebar, and the local component library that keeps domain-specific patterns reusable.

When a product grows one module at a time, the design debt does not show up in any single screen. Every module in WikiPro was defensible on its own; the cost only appeared in the transitions between them, in the moment a user moved from Chat to Payments and had to relearn how a table behaves. That reframed the redesign for me: the unit of work was not the screen, it was the seam between screens, and a shared component system was the only thing that could fix it everywhere at once.

Extending the design system locally turned out to matter as much as adopting it. Align UI covered most of the platform, but Chat needed patterns no general system would carry, and that gap is exactly where one-off UI normally reenters a product. Building those patterns as named, reusable local components instead meant the parts of the platform most likely to drift stayed inside the system.