Summary
Citera’s founder Liam Karlsson accepted a place in the Autumn 2026 Kickstart Fellowship, with the programme confirming the place and available resources in September. The fellowship combines a founder community, workspace access, sessions and individual support. For Citera, its relevance is the opportunity to challenge decisions about the product and the business while maintaining a clear connection between advice, practical experiments and the work customers need us to deliver.
What our Kickstart place includes
Kickstart’s confirmation described access to workspace at Halkin, Paris Gardens in London during the cohort, alongside founder sessions and opportunities for individual check-ins. The programme also outlined support with introductions, customer connections and feedback on the business. Those are resources available through the fellowship, not a claim that we attended every session, moved the whole company to London or received a particular investment. Accepting a place and making effective use of the programme are related but different steps. The distinction helps keep the story focused on what matters. A fellowship can create access to useful people and perspectives, but the founders still need to decide which questions to bring, what to test and how to apply the resulting feedback.
Why we value an ongoing feedback rhythm
A single good conversation can change how a founder sees a problem. A recurring conversation can reveal whether that insight actually changed the business. We see that continuity as one of the useful features of a structured founder programme. For Citera, the questions are practical. Are we solving the customer’s most important growth constraint? Is onboarding asking for the right information? Does the platform complete useful work without creating unnecessary supervision? Can the customer understand the result well enough to decide what should happen next? A regular check-in should return to those questions with evidence. What changed since the previous discussion? What did the customer do? Which assumption became more credible, and which one became less credible? The programme becomes useful when it supports that cycle rather than producing a fresh set of disconnected ideas every week.
The difference between feedback and a roadmap
Founders can hear several persuasive but incompatible recommendations in the same afternoon. One person advises going upmarket, another recommends simplifying for small businesses, and a third suggests expanding into a new channel. Each may be reasonable under different assumptions. Our preferred response is to understand the assumptions before adopting the advice. What customer is the person imagining? What constraint do they think matters most? What evidence would need to be true for their recommendation to make sense? That turns feedback into something we can evaluate. A recommendation to add more automation, for example, may depend on customers already trusting the underlying workflow. If they do not, clearer status and better review controls may be a more useful first step. The right decision depends on the actual problem, not the confidence with which the advice was delivered.
A practical way to use a founder check-in
We would bring one consequential decision rather than a broad company update. The discussion should start with the customer problem, the evidence available and the options being considered. It should also state what remains unknown and why the decision matters now. Consider an illustrative onboarding problem. Some customers connect their website but do not activate publishing. Possible explanations include unclear permissions, lack of confidence in the content or simply not understanding the next step. Each explanation suggests a different experiment. A useful check-in would help sharpen the test rather than jump immediately to a feature. The team might improve the permission explanation, review the first content plan with customers or simplify the activation sequence. The next conversation can then examine what happened, rather than repeat the original diagnosis without new evidence.
Making introductions relevant to the company
Access to a network is valuable when the request is specific enough for someone to help. A founder asking for more customers leaves the other person with most of the work. A founder describing a particular business type and a defined problem gives the introduction a clearer purpose. For Citera, that might mean speaking with a company that has strong expertise but an under-maintained website, or a team that publishes regularly but cannot connect its activity to useful customer outcomes. The introduction becomes a way to learn about a real workflow, not simply another opportunity to present the product. We also want to respect the other side of the relationship. A pilot should have a clear scope and reasonable expectations, and a feedback conversation should not be disguised as an obligation to buy. Useful networks depend on that distinction remaining intact.
Building a company without outsourcing judgement
A founder programme can offer support, but it cannot own the company’s decisions. We remain responsible for the promises we make, the work we prioritise and the way we handle uncertainty. That is especially important in an AI product, where it can be easy to confuse a new capability with a useful customer outcome. A model may enable a feature quickly, but the surrounding product still needs accurate information, appropriate permissions and a dependable way to complete the task. We want external feedback to make those decisions more rigorous, not to create a reason to pursue every new possibility. The strongest result is often a clearer decision about what not to build yet, leaving the team with more capacity to improve the work that matters most.
What the fellowship means for Citera customers
The intended customer benefit is indirect but practical: better product judgement, clearer communication and a more disciplined approach to testing improvements. Fellowship membership itself is not a product feature, and it does not certify the platform’s performance. Customers should continue to evaluate Citera by the work it helps them complete. We want the support around the company to strengthen that work, whether the improvement appears in onboarding, content quality, publishing reliability or the way results are explained.
Frequently asked questions
Has Liam accepted a place in the Kickstart Fellowship?
Yes. The September 2026 programme correspondence confirms acceptance of the Autumn fellowship place and describes the resources available to the cohort.
Does this mean the whole company has moved to London?
No. Workspace access and fellowship participation should not be treated as evidence of a company relocation. The programme relationship can be described without making that additional claim.
Did Kickstart invest in Citera?
This article concerns fellowship participation and support. It does not announce an equity investment or a guaranteed fundraising outcome.
Applying support to the work in front of us
We are grateful for the opportunity to be part of the Kickstart Fellowship. Our aim is to use the programme to ask better questions, test the right assumptions and keep improving the connection between Citera’s product and the work businesses need to do. Explore Citera to see that focus in practice.
Sources and useful links
Citera: organic growth platform
