Back to Blog

The PersonaCart Journey, post 1 of 21 - Introduction

Journey4 min read

The PersonaCart Journey: why we are writing it

A written-up look back at how PersonaCart was built, from 12 April to 12 October 2026. Every claim comes from our real commit history.

V

Vinod Morya

Co-founder, PersonaCart • October 12, 2026

J

This is the first post in a written-up look back at how PersonaCart was built. I am writing it on 12 October 2026. The series covers 12 April to 12 October 2026, and every post after this one is about one period of that time. I wrote them from our git history, not from memory.

In short

  • This series explains, one feature at a time, what we tried to build and what is actually built.
  • PersonaCart is for coaches, academies and studios who also sell things online.
  • Everything described is built and sits on our staging branch. It is not a story about customers or revenue, because we are pre-launch.

Why a journey series

Most software company blogs only show the finished product. We wanted a record that is closer to the truth: what we set out to do in a given fortnight, what the code shows we did, and what is still open.

So the rule for this series is simple. Every claim comes from the commit history of our two code repositories, the Go backend and the React front end. If a commit does not clearly show something a coach or academy owner would notice, it does not go in. Refactors, tests and security internals are skipped, and so is anything that was put on the shelf.

We also do not give numbers about users or sales. We are not launched to customers yet. The people using the product today are mostly the founders and their test accounts. Saying more would be invented.

What PersonaCart is trying to be

PersonaCart is a platform for people who teach and coach: sports coaches, studio owners, trainers, educators. They usually run two businesses at once. One is the physical or live work with students and families. The other is selling: programs, courses, memberships, merchandise, downloads.

We want one place for both, with two parts that stay separate.

  • The store. A storefront with products, courses, memberships and checkout. This is where the first months of work went.
  • The Academy. Teams, rosters, schedules, attendance and a parents' inbox. It is a different part of the product from the store, and a later post explains it on its own. See the Academy page.

Around those two sit a few other tools: a link-in-bio page (BioLink), an AI course generator and a set of free tools. Coaches are free to add to an Academy; for plans, see pricing.

How far back the history goes

The front-end repository's first commit is dated 10 February 2026 and the backend's is dated 17 February 2026. So by 12 April, when this series starts, the code was already about two months old. You will see in post 02 that April was already busy: an AI helper team, a data import wizard, express checkout and a lot of store settings.

The history is not tidy. Some work was started and later pulled back, some was renamed, some was cut from scope on purpose. In the posts I say so when the commits show it. For example, in May we limited the first release of themes to four and pushed the rest to a later version. That kind of decision is part of the story.

How each post is built

Each post has the same shape, so you can skim it.

  • In short. Three bullets.
  • The lead feature. One feature that mattered most in that period, named in the title.
  • What we built. The other things, briefly, in plain words.
  • What it means for a coach or academy. What you would notice, not what the code does.
  • FAQ. Three questions answered only from what the history shows.

Every post says that it is a look back and carries a "Period covered" line. They are all published on the same day, 12 October 2026, so none of them is backdated.

What you will not find here

  • Screenshots of old versions. We did not keep them, and we will not recreate them. Where an image appears, it shows today's product.
  • Customer stories, quotes or growth numbers.
  • Prices. They change and live on the pricing page.
  • Promises about what is next, beyond what the next period's commits show.

What is next

The next post covers 12 to 25 April 2026. Its lead feature is Pie, the AI team inside PersonaCart. After that the series moves fortnight by fortnight until early August, then week by week until today. The last posts explain the Academy and where the product stands now.

If you are a coach or run an academy and want to follow along, start with post 02. If you want something built, my address is at the end of each post.


Want to talk? I am one of the co-founders of PersonaCart. If you have a question, an idea or something you want us to build, write to me directly: [email protected].

Vinod Morya, Co-founder, PersonaCart

Frequently asked questions

Is PersonaCart launched to customers?

No. The code described in this series is built and sits on our staging branch. The people using it today are mainly the founders and their own test accounts, so we do not quote customer numbers.

Where do the facts in these posts come from?

From the commit history of our backend and front-end repositories. Each post has an audit file listing the commits behind every claim. Anything that was shelved or is not clearly visible to a user is left out.

Is the Academy part of the online store?

No. The Academy, with teams, schedules and a parents' inbox, is separate from the store. This series explains it in its own post.

V

Written by Vinod Morya

Co-founder, PersonaCart

Helping creators build successful online businesses with practical tips and strategies.

Subscribe to our newsletter

Get the latest creator tips and strategies delivered to your inbox.

Ready to Apply These Insights?

Start building your creator business with PersonaCart today.

Start freeNot sure yet?

READY TO BUILD?

Join the creators selling on PersonaCart. Start your 14-day free trial today.