Summary
Citera, formerly Rankad.ai, joined Yuncture’s incubator in early 2026. Yuncture’s own reporting documents both our participation and the continued mentorship around the company while Liam Karlsson and William Gyltman spent time at The Residency in San Francisco. The relationship connects two parts of our story: developing the business with a Swedish support network and testing how our product can turn organic growth plans into useful work for real companies.
Our relationship with Yuncture
Yuncture is part of the startup ecosystem in Gothenburg, and our relationship began under the Rankad.ai name. Its March 2026 article describes our entry into the incubator and the support that continued after the founders travelled to San Francisco. A later article followed the company’s return to Gothenburg and the next stage of its platform development. Those public accounts provide a concrete basis for this story. We are not using the relationship to imply that Yuncture guarantees our customer results or that every company in its network is a Citera customer. The relevant connection is company development, mentorship and the opportunity to stay close to businesses working through their own growth challenges. For us, that combination is valuable because the product and the company cannot be developed independently. The quality of our commercial decisions affects which problems we prioritise, and the quality of the product affects whether the relationships around the company lead to lasting value.
What a founder network can reveal about growth
An early-stage business may need customers urgently while still changing its offer, audience or positioning. A larger company may have a clearer offer but struggle to keep its website and content aligned with the work it actually does. Both can describe the problem as needing more visibility, even though the appropriate response is different. We want to understand that difference before recommending more content. A startup that has not settled on its customer should not be pushed into a large publishing plan based on an untested message. A business with a proven service may benefit more from explaining it clearly and answering recurring buying questions than from another broad awareness article.
A network of companies at different stages creates a useful setting for those conversations. The aim is not to collect as many feature requests as possible. It is to identify patterns in the work businesses are trying to do and understand which parts can be made more repeatable.
Making a pilot useful for both sides
Our preferred pilot structure begins with a specific goal and a realistic scope. The customer should know what the platform will help with, what information it needs and what their own involvement will be. We should know which question the pilot is intended to answer and what would make the result worth continuing. For an illustrative B2B company, that might mean improving a small set of commercial pages and creating supporting content around a defined group of customer questions. Before starting, the team would confirm the services being offered, the audience being addressed and the claims that can be supported publicly. The pilot should then make completed work visible. It should be possible to distinguish a draft from a published page, a suggested improvement from an authorised change, and an early visibility signal from a commercial result. That clarity makes the final discussion more useful than a general impression that the software seemed active.
What meaningful onboarding needs to establish
We think onboarding should do more than collect a website address. The platform needs enough context to avoid creating plausible but inaccurate descriptions of the business. That includes the offer, target customers, relevant markets, differentiators and any constraints on language or claims. Connections to publishing and measurement systems also need to be checked deliberately. Connecting the wrong website property or approving more access than necessary creates avoidable confusion later. A customer should understand which account is connected, what the platform can read and what it is permitted to change. A good onboarding conversation ends with an agreed first set of work rather than a long list of features to explore. The purpose is to make the next step obvious and useful, so the customer does not need to reconstruct the plan after the meeting.
Learning without turning every request into a feature
When a company explains a problem, the first proposed solution is not always the best product requirement. A request for a new report might actually reflect uncertainty about what work was completed. A request for more articles might reflect a weak service page. A request for a new integration might be a genuine blocker, or it might be avoidable through a simpler workflow.
Our approach is to trace the request back to the decision or task the customer is trying to complete. That makes it easier to distinguish a broadly useful product improvement from a one-off preference. It also helps us explain why a request is being prioritised, deferred or addressed in another way. This is one reason we value an incubator relationship alongside customer work. A founder needs enough proximity to listen carefully and enough distance to recognise when the company is being pulled away from a repeatable product.
Keeping the pilot review commercially honest
A useful review should account for both the work delivered and the conditions under which it was delivered. If important integrations were connected late, or if content remained waiting for approval, the evaluation should reflect that. Equally, activity alone should not be presented as success when the work did not address the customer’s priorities. We would want the discussion to cover what changed, what the customer learned and which next actions are justified. Where the evidence is early, the answer may be to continue a focused test rather than declare a final result. Where the fit is poor, the honest outcome may be not to continue. That does not weaken a growth product’s value proposition. It makes the relationship more credible by connecting continued use to a useful scope of work rather than to an assumption that every customer should remain indefinitely.
A Swedish base for a broader product ambition
Yuncture’s reporting captures a useful part of our development: international exposure did not replace the Swedish network around the company. The two can serve different purposes. Time in another market can challenge assumptions, while an ongoing support relationship can provide continuity as the team turns those observations into decisions. Our ambition is to build a platform that serves businesses across markets without losing sight of the work each business needs. That means staying attentive to differences in customer questions, approval processes and commercial priorities rather than treating growth as the same checklist everywhere.
Frequently asked questions
Is Yuncture a confirmed part of Citera’s company story?
Yes. Yuncture has published its own accounts of Rankad.ai’s incubator participation and subsequent development. Citera is our current brand.
Does the relationship mean all Yuncture companies use Citera?
No. An incubator relationship should not be presented as blanket adoption across its network. Individual pilots and customer engagements have their own scope and status.
What should a startup aim to learn from a growth-software pilot?
We would focus on whether the platform can complete a useful, agreed set of work with a reasonable amount of customer effort, and whether the resulting evidence supports the next commercial decision.
Building through useful relationships
We value Yuncture’s place in the company’s development and the opportunity to keep learning from the businesses around us. Our focus is to translate that learning into a product that helps companies understand their opportunities and carry out the work behind organic growth. Explore Citera or speak with us about a focused starting point for your own business.
Sources and useful links
Yuncture: Rankad’s incubator and San Francisco story
Yuncture: Rankad’s return and platform development
