U.S. SLED · How we engage

How a subcontract engagement begins.

Three steps from first email to scoped work. NDA on first substantive contact. No exceptions. No public materials are exchanged before paperwork is signed.

The sequence

Three steps. Predictable timing. Same playbook every time.

The structured-relationship sequence is itself the credibility signal. Capture managers and BD leads at U.S. primes know the rhythm; we hold to it.

01
Day 1 to 5

Introduction

Email or LinkedIn introduction from a capture manager, BD lead, or program manager at a U.S. prime. Within one business day, a Techtiz partner manager replies with a mutual NDA template and a 30-minute calendar slot. The reply is from a US-based contact, not an offshore inbox.

02
Week 1 to 2

Capability conversation under NDA

30 to 60 minute call once the NDA is in place. The prime describes the engagement type, the procurement vehicle, the timeline, and any sensitive context. Techtiz describes which Backbone capabilities apply, the team shape, the contracting structure, and any pre-existing engagements that touch the same technical domain.

03
Week 2 to 4

Scoped subcontract conversation

If the engagement fits, Techtiz delivers a scoped statement of work, teaming letter draft, and named-resume options. The prime's contracts team takes it from there. Subcontract paperwork closes within 7 to 14 days for most vehicles. For active pre-award engagements, the teaming letter precedes the SOW.

What we do not do

The boundaries are the credibility.

Every engagement begins with a structured relationship. The behaviors below are out of bounds, full stop. This isn't a sales line; it's how the practice is operated.

We do not solicit RFPs from the open market.

No public CTA inviting unsolicited RFP submissions. No catalog of anonymized RFP analyses published as marketing material. The structured-relationship sequence is the only entry point.

We do not analyze RFPs we have not been formally engaged on.

Strategic analysis of evaluation criteria, statutory requirements, or scoring matrices happens against a defined engagement scope, under NDA, with a prime in the room. Never as public commentary on named, active solicitations.

We do not bid as prime.

Subcontract-only. Direct-to-agency proposals are out of scope. The prime is always the named contractor on the procurement vehicle and the only voice to the agency.

We do not contact agencies directly.

Every engagement routes through a U.S. prime under a master subcontract. We do not appear in agency-facing emails, calls, deliverables, or co-logo footers. If the agency asks who built it, the answer is the prime's name.

Start the sequence

Step 01 is one email.

From a capture manager, BD lead, or program manager at a U.S. prime. One business day later, a US-based partner manager replies with the NDA and a calendar slot.

What to include in the first email

  • Your prime firm name and your role
  • Engagement type (pre-award, post-award, capability)
  • Technical surface area at a high level
  • Timing — active engagement, within 30 days, or pipeline
  • Whether a procurement vehicle is in mind
Locked in teaming letter

Four non-negotiables, in writing.

These show up in the teaming letter draft we send in Step 3. They are not negotiable; they are how the practice operates.

You stay the only voice to the agency.

Never in agency-facing emails, calls, or deliverables. No co-logos, no "powered by" footers.

Your brand on every artifact.

Code, docs, decks, runbooks, and dashboards ship under your prime brand. IP licensed to you for the period of performance.

Compliance posture, kept.

We operate inside your authorization boundary. CJIS, HIPAA, IRS Pub 1075, StateRAMP-aligned controls applied to our work.

Prime PM owns the relationship.

Status, escalations, and change requests flow through your PM. Weekly burndowns to you, never to the agency.

Frequently asked questions

How Teaming Engagements Start

Common questions about our three-step NDA-first sequence and subcontract boundaries.

What is the first step to engage Techtiz as a subcontractor?

A capture manager, BD lead, or program manager at a U.S. prime introduces the opportunity by email or LinkedIn. Within one business day we reply with a mutual NDA template and a 30-minute calendar slot from a U.S.-based contact.

Why is an NDA required before capability materials?

Sensitive procurement context, vehicle structure, and active bid details cannot be discussed in the open. The mutual NDA precedes technical depth, named resumes, or reference conversations. No exceptions.

What is discussed in the capability conversation?

Under NDA we align on engagement type (pre-award, post-award, or pipeline), technical surface area, procurement vehicle, team shape, contracting structure, timeline, and any domain conflicts with existing work.

When does a teaming letter or subcontract SOW appear?

If the fit is mutual, weeks two to four typically include a scoped statement of work, teaming letter draft, and named-resume options for your contracts team. For active pre-award pursuits, the teaming letter often precedes the full SOW.

Does Techtiz publish unsolicited RFP analyses or open solicitations?

No. We do not solicit RFPs from the open market or publish anonymized bid teasers as marketing. The structured relationship sequence on this page is the only entry point.

Can Techtiz white-label deliverables under our prime brand?

Yes. All artifacts (code, documents, demos, and status reporting) are produced for your prime brand. Period-of-performance IP and white-label language are standard in our teaming packages.