Government affairs research keeps moving after the first read. An agency can revise its guidance, a policy page can change, or a procurement deadline can shift. For Locke, useful research means understanding what a source says and knowing when it changes.
Ainesh Mohan, a founding team member and Member of Technical Staff at Locke, uses Context.dev to bring web content into that research workflow. Scraping makes the information usable, and Monitors keep watch on the sources worth following.
What is Locke?
Locke builds AI agents that help companies and governments work together. Its agents power Locke Government Affairs, which helps companies monitor regulations, engage policymakers, and pursue government contracts. The company is part of Y Combinator's Summer 2026 batch.
That work starts with research. The team needs information from across the web in a form its tools can actually use, with a way to keep following important sources after the initial research is done.
Web content the team can work with
Ainesh came to Context.dev with a straightforward use case:
"Mostly wanted this tool for web research. Super useful, quick and consistent, does a great job scraping and preparing data in consumable formats."
Finding a relevant page is only part of the job. The next step is getting its content into a format that can feed analysis, comparisons, and further research.
Context.dev handles that step for Locke. It turns web pages into usable content, giving the team a consistent starting point across sources with different layouts and publishing systems. Ainesh's emphasis was on both speed and the quality of what came back: content that was ready to work with.
About 10 seconds of manual setup
Getting started was a small part of the work. Asked about the onboarding experience, Ainesh said:
"very smooth, took me like 10 seconds of manual work."
For Ainesh, the setup stayed out of the way. Very little manual configuration stood between signing up and trying Context.dev on a research task.
Monitors keep watch after the first scrape
An initial scrape answers what is on a page today. Locke also uses Context.dev Monitors to watch important sources for changes, extending the research workflow beyond that first snapshot.
Monitors check sources on a schedule and record detected changes. That gives the team something concrete to review when a page is updated, instead of relying on someone remembering to open it again.
For government affairs research, the sources worth watching might include agency guidance, policy updates, or procurement pages. A revised requirement or a changed deadline can be the reason to revisit an earlier finding.
The workflow connects three steps:
- Research a source: scrape the relevant page into content Locke's tools can consume.
- Keep watch: use a monitor to check that source for changes over time.
- Review the update: use the detected change as a starting point for follow-up research.
Scraping provides the material for the first pass. Monitoring helps the team recognize when that material needs another look.
The outcome
Asked about the results, Ainesh summed them up in three words:
"High quality research."
For Locke, Context.dev brings together three practical benefits:
- Very little manual setup: Ainesh described getting started as smooth, with about 10 seconds of hands-on work.
- Quick, consistent web research: scraped content arrives in consumable formats for the team's research workflows.
- Ongoing visibility into changes: monitors keep watch on important sources and give the team a reason to revisit its findings.
The result is a research workflow that covers both the initial read and the next update, supporting a team whose work depends on understanding a changing government landscape.
Building research that needs to stay current? Explore Context.dev's web tools and Monitors.
Working with government? Learn more about Locke.