I have omitted and obfuscated confidential information in this design case study. All information in this example is my own and does not necessarily reflect the views of MoxiWorks.

Just Moxi

Moxi Engage

Moxi Engage helps agents and brokerages improve the way they manage their real estate business.

Project Details

  • Company: MoxiWorks (Former Windermere Solutions)
  • Product: CRM Tool
  • Year: 2013
  • Tools:

Agents see 54% more business, on average

Their customer relationship management (CRM) software should nurture real estate sales, not just any sales. MoxiEngage was built for real estate agents, so it aligns with an agent’s workflow, leverages property data, and encourages long-term lead nurturing. What a concept, right?

The goal is to help agents and brokerages improve the way they manage their real estate business.

  • Allow agents to set their income goal within the CRM and receive activity recommendations based on where they are in relation to the goal.
  • Relevant activities and tasks are recommended based on where a client is in the sales cycle. Automated email updates as the user closes transactions.
  • Client data and insights at their fingertips.
  • Responsive application design.

My role

I joined the project during the "Design" process

I participated in the software development life-cycle including: functional definition, interaction models, user interface design, page layouts, content style guides and design patterns, wireframes, prototypes, site maps and navigation schemas


A software productivity solution for real estate agents and brokerages that could be accessed from smart phones, tablets, laptops, and desktop computers.

Research told us that 80% of the time agents are using mobile as a primary work tool. “Mobile First.”

Creating Scenarios

I use scenarios to describe the stories and context behind why a specific user or user group comes use the tool. They note the goals and questions to be achieved and sometimes define the possibilities of how the user(s) can achieve them via the tool.


Tasks wireframes

Each task is explained so stakeholders can review and comment on the design. After the wireframe is approved then I start working on a high-fi prototype where developers can visualize and interact with the design.

  • Actions and elements of each screen.
  • Screen Descriptions.

Communicating Design

I created design artifacts providing the devs the CSS styles and all other definitions to accelerate the building phase and reduce the coding time.

Redline documentation

Reduce Coding Time – This document helped to accelerate the development phase. Redline doc.

Image shows Redlines doc
Redline documentation pdf.


For the prototype I decided to use Axure RP to show the design and interaction of the idea. One of the main reasons why I decided to use Axure to develop the prototype was the limited time that I had to transform the idea into a playable artifact.

Desktop Prototype

Mobile Prototype

Onboarding process


Encourage users to engage with the tools features.

  1. Help them get comfortable by setting expectations for what’ll happen.
  2. Provide an obvious way to move forward to that next step.


From the beginning of the project I was focusing my work trying to understand the necessities of the brokers. I conducted six usability testing sessions to gather data regarding how agents navigate and search for information. I prepared the user testing scripts and I reported and presented findings to the stakeholders.

Project outcome

Six Months after release: 4,789 agents signed for a license.

"One of the best time management tools that I have seen in my 25 years in this business" - John Brauer, Broker

What the community is saying

What the community is saying



  • Difficulty gathering user feedback.
  • Participants were hard to schedule and to commit to participate in our studies.
  • Responsive application design. It was hard to demonstrate to the devs how the tool adapts at different screen widths using AXURE as a prototype tool.

What would I do differently

  • I would have used hand coding instead of Axure as a prototyping tool.
  • Using hand coding would have demonstrated to developers how the tool adapts at different screen widths in a more accurate way. It would have eliminated some miscommunication with the devs.
  • RMore user feedback.

Carlos Marin Burgos
Website Designed and Hand-Coded by Carlos Marin Burgos