Admin
Business Growth
Tech
Last updated on April 11th, 2019
# companies x max(range of revenues)
(Optimistic)
# companies x min(range of revenues)
(Pessimistic)
From Pipecandy’s study we can obtain how the market is distributed per revenue ranges and where Solidus revenue average is within the distribution.
Average Solidus stores revenue
How?
- Our clients
- Surveys
- Online financial statements
- Owler.com data
We are only considering stores that do 100% web sales
Average Solidus stores revenue
Current Solidus adopters are in a market zone that has a lot of opportunities.
No resource to compete with <$1M platforms.
We are not doing wrong.
It's ok to target big stores.
Which features do they want?
Do big stores start as <$1M?
Free Rambling
Direct
Open-source; No Saas; code-quality centered; active community; custom-ecommerce-centered
Indirect
Got a pricing model for custom eCommerce/Saas; plug-in system; straightforward retail experience
We can't consider everything!
How do we choose?
features.each do |feature|
if Competitor.indirect.with(feature).size > 4 or
Competitor.direct.with(feature).size > 1
feature.take!
end
end
Examples
Examples
Communicate Success stories/case studies
indirect: 9
direct: 4
👍
Examples
Multisales channels and omnichannels
indirect: 2
direct: 0
👎
Examples
Free Trial/demo on the website
indirect: 4
direct: 1
👍
Examples
Theme Store
indirect: 7
direct: 0
👎
Medium-Big companies
Can probably spend on development
High-volume stores
Why?
Development firm decision
RoR Background
Open source allowed our company to let our small development team focus on company specific features while leaning on the open source community to support our general eCommerce needs.
We needed something easy to customize.
Why?
No one mentioned a specific feature (promotions, shipping, inventory)
A lot of Spree migrations, because of the community
Tech Roles have a high impact of the decision
Pretty much, but we need to improve
What can be improved?
Abandoned ecosystem that leads to poor backward compatibility & unsolved bugs: 5
Poor documentation: 5
Lacks out-of-the-box features: 4
integration with ERP system
integration with LTL freight shippers
No tutorials available (frontend/backend): 3
Bad UX/UI Admin: 3 ✅
Too complex: 3
Heavy codebase: 2
Where are we doing well?
It’s flexible, scalable, and customizable: 14
Active community: 8
It’s based on Ruby on Rails/Ruby: 7
It’s open-source: 6
It’s solid, performing, and mature: 6
A lot of high-quality extensions: 5
Easy to understand and approach: 4
TDD: 1
How can we improve?
More tutorial/marketing material
Blog posts, screencasts, etc.
More StackOverflow/Knowledge base
Google Search, FAQ
More active development
Core, Extensions
Strengths
🎯 Helpful to achieve the objective
🏠 Internal origin (attributes of the organization)
Weaknesses
⚔️ Harmful to achieve the objective
🏠 Internal origin (attributes of the organization)
Opportunities
🎯 Helpful to achieve the objective
🌏 External origin (attributes of the environment)
Threats
⚔️ Harmful to achieve the objective
🌏 External origin (attributes of the environment)
Transform Weaknesses into Strengths ( ⚔️🏠-> 🎯🏠 )
Transform Threats into Opportunities ( ⚔️🌏 -> 🎯🌏 )
Connect Strengths to Opportunities ( 🎯🏠-> 🎯🌏 )
to make them selling points in the market
Example
Missing demo on Solidus.io
SWOT
(Weakness)
⚔️🏠-> 🎯🏠
Task
Add a demo
on Solidus.io
Do we want to add more tasks?
Do we need a process to add tasks?
💡
One vote per stakeholder?
Weighted vote based on OC contribution?