Welcome to the Product section of the DomiDo wiki. DomiDo is the artificial-intelligence-assisted modular outdoor construction platform built by Avvyland Limited, and at its centre is a single physical idea: a universal block system. Customers describe an idea in plain English, upload a 3D model, or pick something from the gallery, and the platform turns it into a buildable kit composed of those universal interlocking blocks and the matching fasteners. Everything else on the platform — every structure, every category demonstration, every gallery listing — is a user-generated design that consumes blocks and fasteners; the company itself manufactures the blocks and fasteners and nothing else. The pages collected here describe what DomiDo sells, who it serves, how people experience it, how the business and market work around it, and where it sits among the alternatives a customer or designer might consider.
This section is written for everyone who needs an honest picture of the product without having to read an internal team's working notes. A new joiner arriving on day one can use the orientation paragraphs to find the part of the picture they need; an investor can move quickly between the business model, the pricing economics, and the competitive landscape; a designer can read the personas and the journeys their work will reach; and an engineer can trace the use cases their code supports back into the user stories and task analyses that justified the choices. Each page begins with a plain-language orientation and then deepens into the substance.
The pages move outward from "what we are building" to "the world it lives in". The Minimum viable product scope page describes the slice being built first — what ships, what is deliberately out, what gaps remain. The Use cases and user journeys page traces how a person discovers DomiDo, designs something, places a pre-order or an order, receives a kit, and assembles it, across both the primary commerce flow and the supporting flows for returns, support, and the designer side. The Personas and the jobs they hire DomiDo to do page introduces the customer and designer archetypes the product is designed for, the underlying job each is trying to accomplish, and the mental models and anxieties behind the behaviour you see in the journeys. The User stories page is the catalogue of testable behavioural requirements organised by epic, used by product, design, and engineering as the single source of truth. The Task analysis page goes step-by-step through every task a customer or operator performs, with time, cognitive load, failure modes, and recovery paths.
On the business side, the Business model page describes how DomiDo earns: direct kit sales, artificial-intelligence design credits, marketplace commission once the designer marketplace opens, Promo Studio usage, ad boosts, and premium platform features. The Pricing and economics page describes the conceptual unit economics — the cost levers, the volume effects, how shipping flows through, and how the model is expected to evolve at scale — without exposing commercially sensitive figures. The Product strategy page lays out the block-system constraints, the filters that keep designs in scope, the scoring framework that ranks use cases, the catalogue tier architecture, and the staged expansion of the use-case categories the platform enables. The Go-to-market page covers the platform mix, the content engine, the influencer and community plays, the public-relations strategy, and the metrics that guide the launch.
The market section then steps outside the company. The Competitive landscape page maps modular building-block systems, three-dimensional-to-physical conversion services, artificial-intelligence-assisted modelling platforms, outdoor structure makers, design marketplaces, custom manufacturing platforms, augmented-reality assembly tools, and the adult building-block category, and identifies where DomiDo is differentiated. The Competitive user-experience comparison page is the close-up version of that map — how each comparable product feels to use, what DomiDo should adopt, what it should adapt, and what it should deliberately avoid.
You can read the section top-to-bottom on a first pass, or jump directly to the page that matches your question; each page is written to stand on its own.