Skip to main content
Meytal Dahan
Back to insights

GovTech Startups: How Do You Start Working With the Public Sector Without Losing Patience With the Pace?

For founders, GovTech is one of the fastest-growing sectors in the digital world, but it's also one of the hardest to break into. The slow pace of the public sector, complex tenders, and the need to understand public bureaucracy - all of these push many founders out. But those who manage to crack the code enjoy enormous business opportunities, stable contracts, and the ability to create real impact. My experience working on a government project lets me understand what makes a GovTech startup successful. The secret isn't only in the technology - it's in the ability to design a product that connects with the way the public sector thinks. A design that conveys credibility, high accessibility, consideration for every user audience, and compliance with accessibility standards (WCAG) is a necessary condition for getting pilot approval from a public body. Founders who show up with an excellent technological product but a snappy, startup-style design get rejected at the gate. Public bodies need to see a product that feels "mature" - one that can serve citizens across every extreme and withstand public scrutiny. Investing in good design early on is the difference between a startup that wins its first pilot and a startup that spends years circling without a meaningful contract.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Government & Public Sector
FoundersFrom MVP to Full Version

Why GovTech MVPs Don't Look Like Startup MVPs

Founders are taught to ship the scrappiest MVP and iterate in public. In govtech, that instinct can sink you. A citizen service that looks like a beta — or breaks for a screen reader user — loses trust you may never win back. So I redefine 'minimum': not a thin slice of everything, but one complete, accessible, end-to-end path a real person can finish with dignity. Narrow the use cases brutally. Never narrow the quality. Then grow in concentric circles — keep the simple core intact, layer depth around it. Your launch version should be something you'd defend in a public hearing. That's the bar.

Read
Government & Public Sector
CEOsPersonalization & Tailored Models

Personalization That Survives Public Scrutiny

When CEOs hear 'personalization' they picture a consumer feed that learns you. In a public service, that's a liability — citizens didn't opt into being profiled, and any hint of differential treatment invites fairness questions you don't want to answer in public. So I reframe it as relevance, not prediction. Not a model guessing what you want — a service showing each person only what actually applies to them, driven by their situation, not surveillance. A parent sees the parent path. Someone who already applied sees status, not a fresh form. That cuts confusion and call volume, and every tailoring decision stays explainable. The efficiency of personalization, without the consumer-playbook downside.

Read
Government & Public Sector
Project ManagersUsability Testing

Usability Testing as Schedule Insurance for Public Services

Usability testing isn't a threat to your timeline — it's insurance on it. The costly defects aren't the ones found in a session; they're the ones found after launch when the fix means re-planning everyone's quarter. Test early, test on the worst device, and label every finding by whether it blocks the core task. A PMO can schedule around that. It can't schedule around surprises.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.