7 min read
โ
V7 has more than 70 people and a talent team of one. Jake Teagle shows the seven V7 Go workflows behind every stage of hiring, from the kick-off call to a new joiner's first week.

V7 Team
V7 Go
A smarter way to manage due diligence and underwriting
One talent person, a 70+ person company, and V7 Go
At V7, recruiting for a company of more than 70 people is run by a single person on our Talent team, Jake Teagle. That only works because the repetitive parts of the job, the sourcing, the research, the outreach and the admin, run on V7 Go.
We build agents for insurers, finance and real estate firms and enterprises every day. This series is about the agents we build for ourselves. First up: how Jake uses V7 Go across seven workflows, from finding candidates to inviting them into the product as part of the interview.
In his words, it saves hours and focuses on high quality work. Here is where those hours come from.
Jake Teagle walks through the V7 Go workspace he uses to run hiring at V7.
1. The hiring playbook: from a kick-off call to a full plan
Before anyone gets sourced, there's a plan. Every role starts with a kick-off meeting with the hiring manager, and an agent turns that conversation into a complete hiring playbook.
How it works
Record the kick-off. The intake meeting with the hiring manager is captured in an AI notetaker so the transcript is ready as soon as the call ends.
Pull the transcript. The agent fetches it and works out what the role needs: the team, the responsibilities, the skills and the interview stages discussed.
Build the playbook. It creates a parent page in Notion, filed under GTM, Operations or Engineering/Product, with five child pages:
Job description, written in V7's house format
Kick-off notes, grouped into themes with the raw transcript underneath
Role pitch, covering V7, the product, the role, what success looks like, the challenges and the team culture
Interview process, with questions for every stage, from recruiter screen and hiring manager interview to a take-home task and a panel scoring rubric. Each question comes with examples of bad, good and excellent answers.
Sourcing strategy, which feeds straight into the sourcing playbook
Review and share. Jake checks the playbook, and from then on the hiring manager and interview panel all work from the same page.
Why it matters
A kick-off call usually ends with a page of scribbled notes and a week of follow-up writing. Here it ends with a JD, a pitch, an interview plan and a sourcing strategy in one place. Every interviewer knows what good looks like before the first candidate is booked in, and the sourcing page feeds straight into the next workflow.
2. The sourcing playbook: from a role brief to a long list
Every new search starts with a playbook in V7 Go, not a blank LinkedIn search bar.

How it works
Fill in a brief. A short form captures the job title, location and the rough technical skills the role needs.
Turn the brief into a search. The agent batches those inputs into one tight prompt and sends it to Crustdata, an MCP server that pulls LinkedIn profile data.
Review a sample of 10. The first pass returns 10 candidates. Jake reviews them and gives feedback.
Iterate or expand. If the sample is off, the agent rewrites the prompt and tries again. If it is right, it generates the full long list.
Get a spreadsheet. The output is a clean table of every candidate who matches: who they are, which company they work at, and a link to their LinkedIn profile.

Why it matters
The human stays in the loop at the one point that needs judgement: does this sample look like the person we want? Everything before and after that check is automated. The 10-candidate gate also stops the agent from producing a long list of the wrong people.
3. Personalised outreach, written from the profile itself
A long list is only useful if people reply. The second workflow turns profiles into messages worth reading.
How it works
Jake picks profiles from the long list.
V7 Go takes each profile as a PDF, reads it and pulls out the candidate's name and background.
It drafts a LinkedIn message tailored to that person and to the specific role.
Why it matters
Generic InMail gets ignored. A message that references someone's actual experience and connects it to the role gets answered. Writing those by hand for dozens of candidates is where a sourcing day usually disappears; here it takes minutes.
4. A living map of the companies we hire from
Good sourcing starts with knowing where the right people work. Jake keeps a company database in V7 Go, organised by sector.
What it holds for each company
Field | What it captures |
|---|---|
URL | The company's website |
Company summary | A short description of the business |
Business type | What kind of company it is |
Good for | Which roles it is a strong talent pool for |

V7 Go fills in and classifies each company, so the table can be filtered. Hiring an Account Executive for the insurance market in New York? Filter the database and get a focused list of target companies in seconds, then feed it straight into the sourcing playbook.
Why it matters
The database compounds. Every search makes it richer, and every new role starts from a better map than the last one.
5. Market analysis that hiring managers can actually read
Shortlists usually reach hiring managers as a spreadsheet or a wall of LinkedIn links. Jake sends them an interactive briefing instead.
How it works
Starting from a shortlist for a role, Jake works in V7 Go's chat to analyse the candidates.
V7 Go builds a lightweight HTML web app that presents the analysis.
The hiring manager sees, at a glance:
which companies the candidates come from
capability signals for each person
their career backgrounds
a rough first view of fit against what the role needs

Why it matters
It gives hiring managers a view of the market, not just a list of names. Conversations about who to interview start from shared evidence, and they happen faster.
6. An agent in the inbox that runs interview logistics
Several of our interviews ask candidates to come into V7 Go and build their own agent. It is the best way to see how someone thinks with the product. It also used to mean a lot of manual workspace invites.
How it works
An agent runs in the background and reads every email Jake exchanges with candidates.
For each one, it decides whether the candidate has reached the build-an-agent stage and needs an invite.
When they do, it calls a custom skill through the V7 Go API that invites the candidate to an interview workspace.
The candidate gets access straight away and can start building.
Why it matters
No one has to remember who needs access or when. The handoff from email to product happens on its own, and candidates never wait on admin to start their assessment.
7. From "yes" to day one: onboarding on autopilot
Hiring doesn't stop when someone accepts an offer. The weeks between the offer and their first day are where a lot of small jobs pile up, and where a new joiner can feel forgotten. One agent now handles all of it.
How it works
Pull the details. As soon as an offer is accepted, the agent pulls the new joiner's details from our ATS: role, start date, office and line manager.
Line up the people. The agent schedules a Slack nudge to the manager, halfway to the start date, to assign an onboarding buddy. It also schedules a heads-up to the team that sets up tools and accounts, two working days before the start date.
Plan the first few days. It books intro meetings with the right colleagues around everyone's diaries, then builds a first-day plan covering set-up, the schedule, tools and a 30/60/90 plan. The plan goes to the manager a week before the start date.
Tell them where to be. A "Your first day with V7" email is scheduled.
Kick off the bootcamp. On the morning of day one, a second agent books the new joiner into V7's onboarding bootcamp: four sessions with the founders and team leads, spread across their first week.
Why it matters
A good first impression is easy to lose to admin. Here, every new joiner gets the same well-organised start, managers know what is coming and when, and nothing relies on someone remembering a date. The candidate experience doesn't end at the offer letter. It carries on until they are settled in.
What this adds up to
Together, these seven workflows cover the whole hiring journey: planning the role, finding the right people, reaching out, briefing the hiring manager, running the assessment and getting new joiners settled in before their first day.
A few patterns carry over to any team building agents:
Start with a plan, not a search. The hiring playbook turns one kick-off call into a JD, a pitch, an interview plan and a sourcing strategy. Everything downstream works from the same page.
Keep a human at the judgement point. The sourcing playbook checks a sample of 10 before it scales, and the onboarding agent shows every message before it goes out. Those checks make the rest trustworthy.
Connect to the tools you already use. An MCP for LinkedIn data, the V7 Go API for workspace invites, and ATS, Notion and Slack for onboarding mean the agents act, not just answer.
Build assets that compound. The company database gets better with every search, and every playbook makes the next one quicker to write.
Let agents run in the background. The best automation is the one nobody has to trigger, whether that's a workspace invite or a first-day email scheduled weeks in advance.

V7 Team
We enable organizations to create specialized AI agents that analyze, review, and reason over data with transparency, control, and auditability at their core.













