Advanced Connectivity Technology Grant UK 2026: How to Compete for a Share of GBP 15 Million for Network Prototypes

If you build communications technology, network infrastructure tools, security systems, or anything that sits close to the pipes and plumbing of modern connectivity, this funding call deserves your attention. CfI: Advanced Connectivity Technologies (ACT): Call 1 is not one of those vague innovation schemes that promises exposure, networking, and little else. This one comes with real money, a clear mission, and a practical requirement: build something that can actually be tested.

The headline figure is hard to ignore. UK registered organisations can apply for a share of £15 million, including VAT, to create near-term prototype solutions that can be deployed on UK testbeds. In plain English, the funder is not shopping for airy white papers or speculative moonshots. They want technologies that can be put through their paces in the real world, or something close to it.

That matters because connectivity is now basic national infrastructure. If roads move goods and power lines move electricity, networks move everything else: work, healthcare, payments, logistics, emergency services, and plenty more. When those networks are weak, insecure, or wasteful, the consequences spread fast. This call is aimed at fixing that through practical innovation tied to two major goals: secure and resilient networks, and sustainable networks.

It is, however, likely to be competitive. Very competitive. A £15 million pot with a sharp national-interest angle tends to attract serious applicants: telecoms firms, specialist hardware companies, network software businesses, systems integrators, cyber firms, and university spinouts with something testable and timely. But that should not put you off. If your team has a credible prototype plan, a strong delivery route, and a sensible story about why your solution matters now, this is exactly the kind of opportunity worth chasing.

At a Glance

Why This Grant Is Worth Taking Seriously

A lot of innovation calls talk about future potential. This one is firmly about near-term delivery. That phrase may sound bureaucratic, but it tells you something useful: the funder wants projects that are close enough to reality to be built, deployed, and evaluated within a reasonable timeframe. Think prototype with a pulse, not concept art in PowerPoint.

There is also a strong policy signal here. The UK is putting money behind communications systems that are not just faster or cheaper, but more secure, more resilient, and more sustainable. Those are not buzzwords. Security means resisting attack, misuse, or compromise. Resilience means surviving disruption and recovering quickly when things go wrong. Sustainability means reducing energy use, waste, and environmental strain while keeping performance strong.

That combination creates room for a wide range of applicants. Your project might focus on trusted network architecture, more efficient radio technologies, resilient edge systems, low-energy network components, better orchestration software, or tools for operating communications systems under stress. If it can be tested on a UK testbed and tied clearly to these national challenges, it may fit.

What This Opportunity Offers

At the most basic level, this opportunity offers access to a share of £15 million to help organisations turn promising advanced connectivity ideas into deployable prototypes. But the real value is bigger than the grant amount alone.

First, this call supports testable deployment, which is gold in sectors where credibility is earned through performance, not claims. A prototype that has been trialled on a UK testbed carries far more weight with future customers, investors, regulators, and partners than a lab-only proof of concept. If your company is trying to cross the awkward gap between “interesting technology” and “serious commercial proposition,” this kind of funding can act like a bridge over a very expensive river.

Second, it aligns your work with two themes that will remain important for years: network security and network sustainability. That makes your project more than a one-off R&D exercise. It becomes part of a much broader market shift. Buyers in telecoms, infrastructure, defence-adjacent sectors, transport, utilities, and smart systems are all under pressure to make connectivity safer and more efficient. A project funded under this call could put you in a stronger position for procurement, partnerships, or follow-on investment.

Third, the prototype-on-testbed requirement forces useful discipline. It pushes applicants to think about integration, performance metrics, deployment conditions, interoperability, and failure modes. In other words, the messy real-world details that often separate a nice demo from a viable product. That may sound demanding, and it is, but it also means the organisations that do well here are likely to come out with something far more valuable than a glossy report.

Finally, the structure appears to allow a lead organisation to work with subcontractors, including those based overseas if their role is necessary and justified. That gives applicants some flexibility to bring in specialist expertise, niche technical support, manufacturing input, or testing capability without building a full consortium structure around multiple co-leads. For some companies, that simplicity will be a blessing.

Who Should Apply

The formal eligibility is relatively concise: the lead applicant must be a UK registered organisation, and contracts are awarded to a single legal entity only. That means if you’re hoping to apply as an informal partnership, a loose consortium, or a cross-institution team without one clear contracting body, stop and sort that out first. This funder wants one accountable lead.

In practice, the best-fit applicants are likely to be organisations with technical depth and enough operational maturity to deliver a prototype on a live or near-live test environment. That could include established telecoms vendors, network software companies, cyber security firms, hardware developers, systems engineering businesses, and ambitious SMEs with a product that is past the “back-of-a-napkin” stage. A university spinout with a clear commercial route could also be a strong contender, especially if it already has prototype components and a serious delivery team.

Here is a useful way to think about fit: if your idea still depends on several scientific breakthroughs before anyone can build it, this probably is not your call. If, on the other hand, your technology exists in some form already and the funding would help you turn it into a field-testable prototype with measurable performance, then you are much closer to the target.

A few examples make this easier to picture. A company developing a secure orchestration layer for distributed network management could be a strong fit if it can show how the system improves resilience under fault conditions. A hardware firm building lower-energy connectivity components might have a case if it can demonstrate measurable sustainability gains on a testbed. A cyber specialist creating tools that harden network infrastructure against compromise could be well positioned if it can prove relevance to secure and resilient operations.

Subcontracting adds another layer of possibility. Suppose your company has the core technology but needs a specialist overseas manufacturer for a custom component, or a UK-based testing partner with very specific facilities. That may be allowed, provided the contribution is necessary, justified, and compliant with procurement and security rules. The key point is that subcontractors should strengthen delivery, not patch over a weak lead applicant.

Understanding the Big Themes: Secure, Resilient, and Sustainable Networks

Applicants often stumble because they repeat the funder’s language without translating it into project reality. Do not just say your work supports secure and sustainable networks. Show how.

Secure networks are about preventing unauthorised access, manipulation, surveillance, disruption, or compromise. That could involve architecture, software, hardware assurance, monitoring, encryption approaches, identity controls, or supply-chain confidence.

Resilient networks are designed to withstand shocks. That might mean redundancy, graceful failure, rapid recovery, adaptive routing, decentralised control, or systems that continue to operate even when parts of the environment become unreliable.

Sustainable networks focus on energy efficiency, lower material use, better lifecycle design, reduced emissions, and smarter operation. This is not only about being greener in theory. It is about reducing the resource hunger of connectivity systems without trashing performance.

If your proposal can touch more than one of these themes, excellent. But do not force it. A clear, well-evidenced case in one area is better than a muddled pitch that tries to claim everything.

Required Materials and What to Prepare Early

The published summary is short, which usually means the operational detail lives on the Innovation Funding Service page and its application forms. Even before you open the portal, you should expect to assemble a package that proves five things: you are eligible, your technology is credible, your project plan is realistic, your budget is justified, and your security/procurement arrangements make sense.

At a minimum, most applicants should be ready to provide a detailed project description, technical objectives, delivery milestones, budget breakdown, organisational details, and information about any subcontractors. If you are using subcontractors, prepare a tight explanation of why each one is necessary. “They are excellent” is not enough. You need something more like: “They possess a unique manufacturing capability or test expertise unavailable internally, and their role is essential to delivery.”

You should also be ready to articulate the testbed plan in concrete terms. Where will the prototype be deployed? What conditions will it be tested under? What success metrics will you use? What does failure look like, and how will you learn from it? If the application form does not ask all of these questions directly, answer them anyway where relevant. Reviewers tend to trust applicants who think beyond the happy path.

Set aside time to gather commercial and compliance information too. Security requirements are explicitly mentioned, and that is not decorative text. If your project involves sensitive technologies, cross-border subcontracting, or components with potential security implications, you need a clean, well-reasoned explanation of how you will manage risk.

Insider Tips for a Winning Application

The strongest applications usually do not win because they sound smartest. They win because they make reviewers feel safe saying yes. Here are the habits that help.

1. Build around a test, not a theory

This call is about deployable prototypes on UK testbeds. So start with the test scenario. What exactly are you proving? Under what conditions? Against what baseline? If your application reads like a research agenda instead of a demonstration plan, you are making life harder for yourself.

2. Treat near-term as a design constraint

“Near-term” is the funder’s polite way of saying “do not ask us to bankroll science fiction.” Be honest about what you can deliver by the end of the project. A smaller prototype that works is far stronger than a sprawling ambition that collapses under its own weight.

3. Make the national challenge painfully clear

Reviewers should not have to connect the dots themselves. Spell out how your project contributes to secure and resilient networks or sustainable networks. Better still, show the mechanism. For example: your solution reduces network energy consumption by automating power scaling during low-demand periods, or improves resilience by maintaining service during node failure.

4. Explain why your team is the one to do it

This is where many technical applicants become oddly shy. Do not undersell yourselves. If you have prior prototypes, customer pilots, patents, domain expertise, test results, or sector partnerships, say so. Confidence backed by evidence is persuasive.

5. Use subcontractors strategically, not decoratively

A bloated network of subcontractors can make a project look confused. Every external contributor should have a precise role. Think scalpel, not Swiss Army knife. If a subcontractor brings essential specialist value, make that case crisply.

6. Write for an intelligent non-specialist

Reviewers may be technically capable, but they are not living inside your product every day. Skip the jargon soup. If you need technical language, define it in plain English. A good rule: if your commercial director cannot explain the proposal after reading it, it probably needs work.

7. Show that you understand risk like an adult

Every real prototype project carries risk. Pretending otherwise is amateur hour. Instead, identify technical, delivery, supply-chain, and security risks, then explain how you will manage them. Calm realism beats chest-thumping optimism every time.

What Makes an Application Stand Out

A standout proposal usually does four things at once. It presents a real problem, offers a plausible solution, lays out a credible test plan, and shows a clear route to impact. Think of it as a four-legged table. If one leg is weak, the whole thing wobbles.

The problem statement should be specific. Not “networks face many threats,” but something like “current network configurations struggle to maintain service under X condition, creating Y operational risk.” Precision makes competence visible.

The solution should be concrete. What are you building? What is novel about it? Why is it better than current options? “Novel” does not have to mean unprecedented in human history. It can mean a new combination, a more practical architecture, or a better deployment method that matters in the target context.

The test plan should feel grounded in reality. Reviewers want to see that you understand technical validation, operational conditions, and measurement. A good testbed strategy can rescue a decent proposal. A vague one can sink even an exciting technology.

And then there is impact. The funder is not merely buying technical activity. It is buying progress toward national connectivity goals. Show how your prototype, if successful, could move into wider deployment, commercial uptake, or operational use. That future path matters.

Common Mistakes to Avoid

One of the easiest ways to sabotage a good project is to submit an application that sounds like a brochure. Reviewers are not shopping for adjectives. They are looking for evidence. If your proposal is packed with claims like “world-leading,” “transformative,” or “best-in-class” without data or specifics, it starts to feel slippery.

Another common mistake is overreaching. Applicants see a large funding pot and try to cram three products, four use cases, and a grand vision for the sector into one bid. Resist that temptation. A focused project with a clean prototype goal is far more believable.

Poor treatment of subcontractors is another red flag. If their role is vague, unjustified, or suspiciously central to the project, reviewers may wonder whether the lead organisation truly has command of delivery. Remember: the contract goes to a single legal entity. That entity needs to look unquestionably in charge.

Many proposals also fail on the translation problem. They may be technically strong, but they do not clearly tie the work to secure and resilient or sustainable network outcomes. If the alignment is weak, the application can feel clever but irrelevant.

Finally, do not leave compliance thinking until the end. Security and procurement requirements are explicitly mentioned. That means reviewers may look closely at who is involved, why they are involved, and how risks are handled. Messy compliance is one of those avoidable errors that makes everyone nervous.

Application Timeline: Work Backward From 3 June 2026

The deadline is 3 June 2026 at 11:00 AM, and if you have applied for UK innovation funding before, you already know the portal will not care that your finance lead was on holiday or your technical diagram needed one last fix. Work backward ruthlessly.

If possible, begin serious preparation eight to ten weeks before the deadline. In the first two weeks, decide whether the project truly fits the brief. That sounds obvious, but it saves enormous pain. Confirm the lead entity, identify any subcontractors, and map the core prototype and testbed concept.

By about six weeks out, you should have a first draft of the technical case, a rough budget, and a delivery structure. This is the moment to stress-test the idea internally. Ask difficult questions. Is the prototype realistic? Is the testbed defined? Does the project clearly serve the stated grand challenges?

At four weeks before deadline, move from ideation to refinement. Tighten the language, sharpen the evidence, and make sure technical, commercial, and compliance sections do not contradict each other. If you are involving subcontractors, gather the justification and cost details now, not during the final scramble.

In the final two weeks, shift into review mode. Check every number, every date, every named partner, every claim. Make someone outside the project team read the application and tell you where they got confused. Submit early if you can. Ten minutes before deadline is not a strategy; it is a hostage situation.

Frequently Asked Questions

Can a non-UK organisation apply as the lead?

No. Based on the published eligibility summary, the lead must be a UK registered organisation. Overseas organisations may participate as subcontractors if their involvement is necessary, justified, and compliant.

Do I need partners to apply?

Not necessarily. A UK registered organisation can apply alone or work with subcontractors. That said, if specialist expertise is needed for delivery or testing, carefully chosen subcontractors may strengthen your bid.

Is this more like research funding or product development funding?

It leans strongly toward applied development and demonstration. The emphasis on near-term, testable solutions and deployable prototypes suggests the funder wants practical outputs rather than early-stage exploratory research.

What does a UK testbed mean in practice?

A testbed is a controlled or semi-realistic environment where you can deploy and evaluate a technology. In this call, the important point is that your prototype should be suitable for testing in the UK, under conditions relevant to the challenge your project addresses.

Can I use overseas subcontractors?

Yes, according to the summary, but only if their role is necessary and justified, and they meet procurement and security requirements. Do not include an overseas subcontractor casually. Make a strong case.

Will a very early-stage concept be competitive?

Probably not. This looks aimed at solutions that can be built into deployable prototypes in the near term. If your idea is still mainly theoretical, it may be too early.

Is the full £15 million available to one project?

The wording says organisations can apply for a share of £15 million, which strongly suggests multiple awards are possible. Check the official application page for the latest details on project size, scope, and funding limits.

Final Thoughts: A Tough Grant, but a Smart One to Pursue

This is a serious opportunity for serious builders. The money is substantial, the national relevance is obvious, and the prototype requirement means success here could carry real weight beyond the grant itself. It is not a call for dreamers with a few nice slides. It is a call for organisations that can design, justify, build, and test.

That makes it demanding. Good. The best funding rounds usually are. If your team has a solution that can strengthen secure and resilient networks or make connectivity more sustainable, and if you can prove it on a UK testbed, this is exactly the kind of competition that can move a company forward.

How to Apply

Ready to apply? Start by reviewing the official opportunity page and then follow the link to the Innovation Funding Service, where the full application details and submission process will be available.

Before you begin, make sure you have confirmed your eligibility, chosen your lead legal entity, scoped any subcontractor roles, and drafted a practical prototype-and-testbed plan. Do not wait until the final week to sort out budgets, security considerations, or technical evidence. This call rewards applicants who look organised from the first paragraph.

Visit the official opportunity page here:
https://www.ukri.org/opportunity/cfi-advanced-connectivity-technologies-act-call-1/

If the project fits, move quickly. Good applications are rarely written in a weekend.