Skip to content
Go back

Mark Product Requirements

Table of contents

Open Table of contents

Second Product Concept

But after I share the concept with my partner, I relize that the most priority and to do first is market validation. How we can build it as fast as possible, until it is ready to be used by the user.

From those feedback, I decide to change into this point

  1. Chat: The most important and main feature is chat. How we can design and manage the chat process as what user need as a business analyst.
  1. Connections: We don’t need to build it self service connection. We can just start manually connect it to the current data source by myself.

  2. Custom Command: We don’t need to build it at first. We can just build it by myself. Because the business user is not tech savvy which they want to customize. Instead, they need as best as possible to provide them with business analyst assistant. That’s all.

With that in mind, this is our new requirements for Mark.

## Overview

Mark is a Business Analyst Assistant designed to empower users by leveraging rich data from various sources to provide actionable insights and assist in decision-making. Mark is strong in helping the user to **Go beyond the numbers** by giving perspective recommendation for the user (For instance, not just product A is declining, but why and how to improve it).

For giving a good decision, Mark need context on the user's business. Therefore, Mark will get data from

1. **BigQuery**: Which is the data warehouse of my first user have currently.
2. **Attachment**: Which the user can upload the file and Mark will extract the data from the file.

Closing

With the fact that we are an engineer, it is often will leads us to over complicate the product and forget about the priority. We need to remember that we are building the product for the user, not for ourselves. So market validation is the most important thing to do at first.


Share this post on:

Previous Post
Mark Agentic Plan
Next Post
Mark Project