The product roadmap did not start as a portfolio
We did not set out with a plan to build several separate products. While building and running Throughout, we encountered recurring problems. Some were internal; others appeared in the businesses we worked with. We began building solutions instead of accepting the same workarounds indefinitely.
Throughout remains the company where we build dedicated engineering teams, software, and AI solutions. Rankout, Comflo, and Checkout are products within that work. Keeping that distinction clear helps explain why their audiences and capabilities differ.
Rankout: connect search work with implementation
In my posts, I introduced Rankout as an effort to make SEO more transparent and measurable. The intention extends beyond showing an audit: help businesses research, implement, measure, and improve search visibility.
Its focus includes SEO, answer engine optimisation, and generative engine optimisation. The important product question for me is whether a business can understand the work that follows a finding. Visibility scores alone are less useful if nobody knows what to do next.
Comflo: connect conversations with business operations
Comflo grew around businesses working through WhatsApp and the operational tasks connected to those conversations. A conversation may involve an order, a product question, or a customer workflow. Treating each as unrelated work makes it harder to keep the context together.
The direction is to make those everyday activities simpler to manage. The product is still developing, so its current website is the place to check availability. A product idea or a feature discussed in a founder update should not be mistaken for a guarantee that everything has shipped.
Checkout: simplify the work around a sale
Throughout Checkout focuses on POS and everyday retail operations: sales, products, inventory, and the business work around them. These are familiar tasks, but the connections between them matter to someone running a shop.
As with the other products, the aim is to solve an observed problem properly rather than add a feature simply because we can build it. The current product page explains its supported setup and distinguishes available features from its roadmap.
An internal tool is a starting point, not product proof
While building Throughout, we also created internal recruitment and operational workflows. Those systems taught us about the friction in our own business. They did not automatically prove that a wider market wanted the same tool in the same form.
Building for other people introduces another question: does the product fit how they work well enough that they choose to keep using it? That is why testing, feedback, and changes remain part of the work. We are still early, and the product direction can develop as we learn.
What connects the products
The common thread is a preference for starting with a real problem. Search visibility, customer operations, and retail selling are different domains, but each contains repeated work that can become clearer with useful software.
I want these founder notes to document what we are learning, not just announce launches. Building software is one part of the challenge. Understanding why someone returns to it is the part we need to keep working on.
What to take away
- Throughout is the company; Rankout, Comflo, and Checkout are products.
- Start with recurring problems rather than an arbitrary feature list.
- Treat user adoption and feedback as questions to investigate.