Crowdfunding works best when it is more than a preorder page. For Smart Companion, the Journal can become a public record of why the product exists, what has been tested and what still needs to be solved before a launch is responsible.
Progress should be visible before the campaign
Rather than appearing with a finished story overnight, we want to document the path. Early updates can cover the intended user experience, industrial design studies and assistant use cases. Later entries can move toward functional prototypes, reliability tests, manufacturing decisions and software readiness.
A milestone-based story
- Experience definition: clarify the daily problem and the smallest useful set of interactions.
- Prototype learning: test form, audio, controls, charging and desktop behavior.
- Software validation: evaluate assistant flows, companionship boundaries and growth programs.
- Production preparation: confirm suppliers, compliance work, quality checks and realistic costs.
- Campaign readiness: publish what is final, what may change and what support actually funds.
Trust grows when progress updates include the difficult decisions, not only the photogenic moments.
Where the community can help
Readers can tell us which routines matter, how much customization feels useful and which accessories deserve priority. Feedback can guide choices, but it should not be treated as a promise that every suggestion will ship.
What we will not claim too early
Until testing and supplier work are complete, final pricing, battery behavior, software scope, delivery timing and production volume remain open. A future crowdfunding page should distinguish confirmed specifications from targets and concepts.
The role of the Journal
Each entry will be dated and focused on one meaningful question. Together, the archive can show the evolution of the product and give future supporters a clearer basis for deciding whether the project is right for them.
QUESTIONS, ANSWERED
Questions about the future crowdfunding path
Has a crowdfunding date been set?
No. A responsible date depends on functional prototypes, supplier work, testing, compliance planning and realistic costs. HugCubs will publish a date only when those foundations are ready.
What will future supporters be able to see?
Updates should cover experience decisions, prototype learning, software validation and production preparation, while clearly separating confirmed specifications from goals that may change.
Can community feedback change the roadmap?
Feedback can help prioritize routines, customization and accessories. It informs decisions, but it is not a promise that every suggestion will become a shipping feature.
