Build your idea.
Strengthen your business.

The most useful first conversation is specific. Explain who struggles with the current situation, how they deal with it today and why a change would matter. A founder who understands the problem can learn the technical choices; a sophisticated technical concept still needs a reason for customers to adopt it.

We assess the founder’s commitment alongside the opportunity. This includes time for customer interviews, access to relevant expertise, openness to difficult feedback and the ability to make decisions. Incubation is collaborative work, so responsibilities and availability need to be realistic.

• Identify a user and the person or organisation likely to pay.
• Explain the present cost, delay, risk or missed opportunity.
• Describe the data or domain knowledge the solution would require.
• Name the assumptions that could make the idea fail.
• State what you have already tried and what you learned.
• Tell us what support you need and what you can contribute.

We agree the next useful stage rather than promising a complete business on day one. The scope can expand when the previous stage provides sufficient evidence. If customer interviews contradict the original idea, revising the proposition may be a better result than building the wrong product.

A good teaser helps a prospective customer, partner or investor understand why the idea deserves a fuller conversation. We can help develop a non-confidential summary that explains the problem, the proposed response and the next milestone. It should make the business easy to understand without overstating traction or revealing protected technical detail.

The message changes with the audience. A customer needs to understand the effect on their work. A partner needs to understand their role and commercial interest. An investor needs to understand the opportunity, the evidence, the financing requirement and the uncertainty. One presentation rarely answers all three equally well.

• A clear problem and defined initial customer.
• The product’s practical value and an explanation of existing alternatives.
• The current stage, supported by accurately described evidence.
• The founder’s contribution and the capability still needed.
• A plausible revenue model and next milestone.
• A specific request: pilot access, a commercial conversation, expertise or capital.

The first build should test the most important uncertainty. For a document product, that might be whether users can retrieve the correct information with an acceptable review burden. For a sales workflow, it might be whether a team follows up more consistently while retaining control of customer communications. The test is chosen before development begins.

We define the starting position, the intended user, the permitted data and the measure of success. We also consider the cases the system should refuse, refer or leave to a person. At review, the decision uses evidence from the pilot, including failures and operational costs, rather than a polished demonstration alone.

A venture needs more than a revenue forecast. Estimate the cost of reaching a buyer, setting up their account, running the software, reviewing AI output and providing support. A product that appears profitable before human supervision or implementation is counted may need a different price or delivery model.

During discovery, use ranges and identify uncertain inputs. During a pilot, replace assumptions with observed usage and delivery effort. The aim is to understand the contribution from each customer, the cash needed before payment arrives and the number of customers the team can support without a matching increase in manual work.

Possible support includes commercial development, technical expertise, training, platform access and product delivery. Selected ventures may be considered for financial support or paid development capacity. Any salary, stipend, credit allocation or investment must be expressly confirmed; it is not an automatic benefit of applying.

The agreement should distinguish your existing intellectual property from new work, identify the owner of the resulting product and define any licence or commercial participation. If an equity relationship is proposed, it is considered separately from service fees. Ask how decisions are made, what happens if a milestone is missed and how you can continue using agreed outputs if the partnership ends.

All training is delivered by Kent Business College, UK. A module consists of 14 weekly sessions of two hours: 28 live learning hours. Depending on your role, relevant learning might include AI agents, n8n automation, databases, AI engineering, project management or leadership.

Training complements practical venture work. You still need time between sessions to apply ideas, review customer feedback and complete agreed actions. The proposal identifies which learning, if any, forms part of the engagement and how it supports the founder’s responsibilities.