Ascension Venture Partners Three layers. Read top-down: the IP underneath, the cadence in the middle, the surface customers touch.
Proprietary map of US defense autonomy. Eighteen months in the making. Quarterly revisions.
AVP runs against a structured map of US defense autonomy: ten named technical sub-segments across three tiers, with named role types, comp band ranges, hiring patterns, and talent clusters per segment. The taxonomy is the asset. Eighteen months in the making. Quarterly revisions.
Behind each sub-segment sits a bench — pre-qualified specialist candidates organised by discipline and by alumni-network source (CMU NREC, MIT Lincoln Laboratory, Anduril, Palantir, SpaceX autopilot, Tesla autopilot, Cruise, Waymo, Navy/SPAWAR, defense-prime alumni). The bench layer is proprietary; the taxonomy is published.
Read the published taxonomy in full at the Warfront publication. The proprietary edition adds candidate benches, contact-level intelligence, exact comp data, and signal triggers.
Six named AI employees. Ten playbooks. Built progressively.
Between the substrate and the customer-facing surface sits the operating layer — six named AI employees, each with defined inputs, outputs, and approval gates, running a fixed set of playbooks. The layer is built progressively. Some employees run autonomously today; others operate with a human-in-the-loop until the underlying data is consolidated. The progression is named explicitly per employee.
Maintains the taxonomy and the bench substrate.
Scans hiring data across the active target list and surfaces trigger events.
Generates sub-segment-aware sequence copy and proposals.
Inbound qualification and scoping.
Candidate validation against role-specific criteria.
Placement lifecycle and post-placement retention support.
The architecture is the product. The named playbooks running across the six employees are the ten plays AVP runs end-to-end.
Three tiers. Priced and scoped distinctly. Most engagements anchor on Tier 1.
AVP delivers across three tiers. Each tier is priced and scoped distinctly. Most engagements anchor on Tier 1 with optional Tier 2 / Tier 3 add-ons.
Operators embedded inside the customer's organisation. Hands-on execution against named hiring briefs. Fractional commercial and operations support where the customer is pre-VP-of-People. The work is recruitment, framed as embedded capability — not search, not staffing.
Anchored on the Warfront taxonomy and bench. Direct hiring-manager access required. Outcome: closed placements with retention support.
AI agent workflows, automation, and operating cadence built into the customer's hiring and GTM motion. Reduces the need for headcount expansion in recruiting, talent operations, and outbound. Architected around the same six-AI-employee model AVP runs internally.
Deployed in parallel to embedded capability or as a standalone engagement. Scope envelope set per workstream — agent specification, integration, run-rate maintenance.
Org design, priority hire sequencing, growth-bottleneck diagnosis. Where the customer's hiring problem is actually an organisational design problem. Where founders need a second pair of eyes on the next twelve months of headcount and the dependencies that gate it.
Higher-touch, lower-volume. Anchored on AVP's principal as the named operator. Useful for pre-Series-B companies preparing for the next financing round and the org expansion that follows.
An operational standard, not a preference.
AVP requires direct hiring-manager access and named-partner status for all placements. Partner-mediated, white-label, or routed arrangements are out of scope.
This is an operational standard, not a preference. The work depends on direct conversation between AVP's operator and the named hiring manager. The constraint protects placement quality and retention; it also keeps AVP's accountability surface clean.
The scoping conversation confirms direct access before any candidate work begins. Engagements that don't satisfy the constraint are declined or referred.
The substrate, the operating layer, and the delivery surface are one system. The Warfront publication shows the substrate; this page describes the layer above; the engagement page is where the surface meets the customer.