← Back

Solo founder

MS Planner to Jira

Researched the Atlassian ecosystem, found an unserved need, built the product, and grew it to 300+ active installs with paying B2B customers. Solo, organic.

Finding the gap

1
Keyword scraper
What people actually search for in the Atlassian ecosystem
2
Forum scraper
Thousands of threads — views, comments, engagement signals
3
AI labeling
Classified every thread as a potential product idea
4
Gap analysis
Cross-referenced demand with existing apps and their installs

One clear winner: MS Planner to Jira integration. The single most wanted problem with zero dedicated solutions.

Building it

Two months from zero to a working product. One person, full scope:

ArchitectureData modelOAuth flowsJira APIMS Graph APIDataverse APIFrontendDeployment

The Microsoft side was especially painful — the Dataverse API for Planner Premium is barely documented. Weeks of trial and error to get the right combination of endpoints and permissions. First version was rough, but it did the core job: tasks sync without copy-pasting.

Product-market fit

People downloaded an app with zero installs and zero reviews. When something didn't work, they didn't leave — they reached out asking to fix it. Willing to work with a rough product because the pain of manual syncing was that bad.

Recruited a developer to help scale. Iterated on every customer conversation — added custom field mapping, two-way sync, and became the first connector to support MS Planner Premium via Dataverse.

Where it is now

300+
Active installs
RISING STAR
Atlassian Badge
4/4 ★★★★
Customer rating

Zero marketing spend. Every customer found it organically.