Get started

Government buyers rarely respond to cold pitches, but they talk openly about their problems in a handful of professional communities. If you show up as someone who understands their constraints, like budgets set a year out, procurement rules and council approvals, you can earn conversations that turn into pilots. Here are the places to start this week, and how to behave in each.

All guidesFor founders of a govtech startup

1. GovLoop

GovLoop is a free community and content site for public servants at federal, state and local levels. Create a profile with your real name and company, then read the discussions and blog comments in your topic area, such as permitting, records or IT modernization. Write one useful post or comment a week drawing on what you have learned, for example: "Three questions I'd ask before replacing a paper permit process, based on 20 interviews with county staff." Never pitch directly. Let people find your product through your profile.

2. ICMA Connect and the Knowledge Network

ICMA is the professional association for city and county managers. Some of its online resources are open to non-members, but discussion areas may require membership. Read the threads and resource libraries to learn the exact language managers use for your problem. Where vendor participation is allowed, answer questions with practical detail and say clearly that you are a vendor. A good reply opens: "Disclosure, I build software for this, but here's what I've seen work regardless of tool."

3. Code for America community and local brigades

Code for America runs a community network of local civic tech groups, often with Slack workspaces and public meetups. Members include volunteers, civic technologists and city staff, many of whom know who owns a given problem inside a government. Join your local group's Slack, introduce yourself in the intro channel, and contribute to a project before asking for anything. After a few weeks you can ask: "Does anyone know who handles 311 intake at the city? I'd love 20 minutes to learn how it works."

4. r/PublicAdministration and r/sysadmin

r/PublicAdministration has public employees and students discussing how government actually runs. r/sysadmin is huge and includes many government IT staff. Both communities ban self-promotion, so read the sidebar rules first. Search for your problem, for example "sysadmin county government legacy software" or "public administration permitting backlog", and answer existing threads with specifics. Ask research questions, never sales questions: "Gov IT folks: what made the last vendor you onboarded actually stick?"

5. State municipal league and association listservs

Almost every state has a league of cities or county association, such as the League of California Cities or the Texas Municipal League, plus role groups for clerks, finance officers and GIS staff. Many have member listservs and directories, and some sell vendor or associate memberships. Start by reading their public event agendas and newsletters to see which problems come up again and again. Then email the association staff and offer a free, non-sales webinar or a short write-up on a topic their members keep raising.

6. Route Fifty and Government Technology

Route Fifty and Government Technology (govtech.com) are newsletters read by state and local leaders. Subscribe to both and keep a list of every official quoted on your problem, since these are people already willing to talk publicly. Send a short, specific email: "Saw your comments in Route Fifty on permit backlogs. I'm researching how mid-size cities handle intake. Could I ask you three questions by email?" Reporters also take story tips, so share a real insight rather than a press release.

7. LinkedIn, by job title

LinkedIn is where government staff are easiest to find by role. Search titles like "City Clerk", "Chief Information Officer" plus "County", "Procurement Officer" or "Director of Public Works", filtered to one state. Comment thoughtfully on their posts for a week before sending a connection request with a note: "I'm building a tool for clerk offices and learning how records requests get handled. Would you share what slows yours down?" Focus on smaller cities first. They have fewer layers of approval and often decide faster.

8. Keep a daily rhythm

Pick two of these places and spend 30 minutes a day reading, answering and logging who you talked to. Track every person, their role, their government and their problem in a simple sheet, because govtech deals move slowly and follow-up wins. Hulby, an AI cofounder, can do this daily for you by finding relevant threads and people and drafting replies for you to review.

Mistakes to skip

  • Pitching in your first post instead of answering questions and disclosing you are a vendor.
  • Targeting federal agencies first, when smaller cities and counties can often buy faster with less paperwork.
  • Ignoring the budget cycle and pushing for a decision months before the next fiscal year.
  • Skipping community rules, which gets you banned and remembered in tight professional circles.

Want this done for your govtech startup, every day?

Hulby finds the people asking for what you built, writes every reply and email, and keeps you on it until they pay. Free to start.

Find my first customers

Questions

Are government employees allowed to talk to vendors?

Generally yes, especially for research and outside an active procurement. If a formal bid is open, they may be restricted, so ask early.

Which buyers should I target first?

Department heads and IT leads in smaller cities and counties. They feel the pain directly and often face fewer approval layers.

Do I need to pay for association memberships?

Not at first. Free newsletters, public forums and LinkedIn are enough to find your first conversations.

How long until a conversation becomes a customer?

It varies widely. Small, low-cost pilots tend to move faster than large contracts, so offer a low-risk first step.