Skip to content

Welcome

Marketrix learns your product by autonomously using it. Connect your web app, and Marketrix explores it through Simulations, builds up Personas and Skills, and accumulates an understanding of how your product actually works. Five tools then run on top of that understanding — three for customer experience, two for engineering.

Every Application in Marketrix rests on the same foundation:

  • Workspace — Your team’s home in Marketrix. Workspaces contain your Applications and the people who can access them.
  • Application — A web app or website you connect to Marketrix. Everything else lives under an Application. See Applications.
  • Knowledge — What Marketrix reads about your product: documents and videos you bring in so it understands your features, terminology, and workflows. See Knowledge.
  • Persona — A model of one of your real user types. Marketrix derives Personas from your audience and runs Simulations as them to surface how different users experience your product. See Personas.
  • Simulation — An autonomous browser session where Marketrix explores your Application and records everything it sees and does. See Simulations.
  • Skill — A reusable browser-automation routine Marketrix distills from completed Simulations. See Skills.
  • Graph — What Marketrix sees: the Application Graph aggregates everything learned across all Simulations into one knowledge and experience graph of your product. Open it with View Graph from any Simulation. See Graph.

The foundation is shared. The five tools built on it are grouped the way the dashboard groups them.

CX Tools

  • Run User Studies — Point your Personas at your product as UX Research, a Survey, or an A/B Study, and read back what each persona did, said, and decided.
  • Interview real users — Send a question set to actual people as an ephemeral link; they answer by voice or text and the transcripts land back in the dashboard. See User Interviews.
  • Support your users in-product — Deploy a Widget that answers questions and guides visitors in three interaction modes — Tell, Show, and Do. See User Support.

Dev Tools

  • Test with QA Flows — Turn requirements into persona-driven Journeys and run them against your app as QA Runs, each Journey judged passed, failed, or indecisive. See QA Flows.
  • Automate with Workflows — Connect GitHub, Slack, or a timer and have Marketrix act when something happens in the tools you already use. See Workflows.