Storemapper
No-code store locator maps for merchant websites.
Business overview
Public positioningNo-code store locator maps for merchant websites. On 2015-02-03 Tyler described personally handling coding and support, with two part-time hires planned. This supports the historical solo stage, not current staffing.
How it makes money
Recurring subscriptions with tiers based on locations and features.
Business breakdown
Researched Oct 19, 2026Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.
The customer problem
Editorial analysis: a merchant with physical stockists needs a maintained location finder without commissioning a custom map for every website.
Core workflow
- Upload store locations and configure the map's appearance.
- Embed the locator in the merchant's website so shoppers can search nearby locations.
- Maintain location data and select a subscription tier for the required capacity and features.
What customers pay for
Editorial analysis: accurate store discovery is the customer outcome; location capacity provides an understandable packaging boundary. Test whether merchants will pay to avoid maintaining this themselves.
Distribution signals
Observed channels and entry points; their performance is not inferred.
- Search and embedded attribution
The founder described organic search and attribution links as acquisition channels; present effectiveness is unverified.
Evidence
Trade-offs
- Editorial analysis: a small feature surface still requires reliable map rendering, clean location imports, and responsive merchant support.
- Editorial analysis: location-based tiers should track customer value without making ordinary store updates a purchasing obstacle.
Open questions
- Which merchant segment has inaccurate locator pages today and will pay for ongoing maintenance?
- Can a narrow integration reduce setup and support enough for one operator?
A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.
Revenue evidence
Founder disclosure- Reporting period
- Historical ARR milestone disclosed February 3, 2015; before the 2017 sale
- Figure as of
- Not provided
- Reporting method
- Founder disclosure
- Source checked
- Oct 19, 2026
- Source published
- Feb 3, 2015
Founder stated a 100K annual recurring revenue milestone. The source publication date is known; no exact accounting cutoff is supplied. VentureLens has not audited payments. The 2015 solo-stage case predates the 2017 sale to SureSwift Capital and does not establish present ownership, team size, or revenue. The income source uses $ without an explicit currency code; preserved as Unspecified $ and excluded from USD comparisons.
Tyler Tringas founder blog: Storemapper 2015 RoadmapPricing
Pricing pageMicro: USD 24.99/month or USD 249/year; official pricing checked 2026-10-19.
The source page may change its prices, limits, or offer after the recorded check date.
What founders can learn
Editorial notesA narrow merchant problem can support subscription revenue; the founder described organic search and embedded attribution links as acquisition channels, then planned to delegate maintenance and support.
These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.
Source material
4 sources- Storemapper official website Public source · Checked Oct 19, 2026
- Founder ARR and solo-stage operating disclosure, 2015-02-03 Public source · Checked Oct 19, 2026
- Founder acquisition account, 2017-10-03 Public source · Checked Oct 19, 2026
- Official current pricing Public source · Checked Oct 19, 2026