PART 1 - WHY DUAL SITE

Why a Dual-Site Strategy? US SLED Page + Regular Site

The opening argument for today’s live demonstration. The 6 reasons to cover before opening Lovable. Every participant must understand why before they build.

2×

Shortlist rate with SLED page

3-5×

Conversion vs generic page

60%

Higher SEO ranking

8 sec

Time to lose a wrong visitor

The 6 Reasons - Cover These First

US Government Buyers Think Completely Differently

A US state procurement officer or prime contractor BD director who lands on a generic Pakistani IT company website sees outsourcing - not a SLED partner. The language, case studies, trust signals, and visual tone all need to speak exclusively to US government procurement culture. One generic page cannot do this.

80% of US government procurement decisions are made before the first call - based entirely on the vendor’s digital presence.

Two Completely Different Buyer Journeys

International clients want: technology portfolio, team size, pricing competitiveness. US SLED audiences want: NAICS codes, SAM.gov registration, past performance with state agencies, compliance awareness, prime contractor teaming experience. One page cannot serve both without failing both.

A visitor who sees irrelevant content leaves within 8 seconds. Two targeted pages convert at 3–5× the rate of one generic page.

SEO and Search Intent Are Completely Different

When a Texas DOT officer searches “IT subcontractor state government website redesign” they get different results than when a Gulf startup searches “affordable web developers Pakistan.” One URL cannot rank for both. Separate pages with separate content strategies each dominate their own search intent.

Targeted landing pages rank 60% higher for specific search terms than generic company homepages.

Trust Signals Are the Opposite for Each Audience

US SLED trust signals: SAM.gov UEI, NAICS codes, WCAG compliance, CMMC awareness, US phone number, state agency past performance. International trust signals: portfolio variety, team photos, global brand logos, responsiveness. Mixing them dilutes both.

US prime contractors are 4× more likely to initiate contact when they see SAM.gov and NAICS data prominently on the landing page.

The CollabP Case Study System Needs a Dedicated Home

The CollabP-issued project experience - the case studies, prime contractor relationships, state coverage - all lives on the US SLED page. This portfolio proves SLED expertise. It must be separated from general portfolio work so evaluators and primes can find it instantly, not buried among unrelated international projects.

Proposals referencing a dedicated SLED portfolio page are shortlisted at 2× the rate of proposals that do not.

You Serve Two Markets Simultaneously - Do Not Choose

You do not need to choose between your existing clients and US SLED ambitions. The dual-site strategy lets you serve both simultaneously - same company, same team, two positioned faces. The regular site keeps existing revenue. The SLED site builds new revenue. They reinforce each other without confusing either audience.

Companies with dedicated vertical landing pages grow that vertical 2.3× faster than companies using a single generic homepage.

Visual: What Each Page Contains

🇺🇸 US SLED Page - /us-sled

AUDIENCE: US Prime Contractors + State Agencies

✓ Hero: “Trusted U.S. SLED IT Partner”
✓ SAM.gov UEI number - prominent
✓ NAICS codes listed
✓ US phone number in header
✓ State coverage map (which states served)
✓ Prime contractors worked with (logos/names)
✓ SLED case studies from CollabP projects
✓ WCAG / CMMC compliance signals
✓ “Partner With Us” CTA for primes
✓ Link to capability statement PDF

🌍 Main / International Page - /

AUDIENCE: International + Pakistani Clients

✓ Hero: General company value proposition
✓ Full service portfolio
✓ International client logos
✓ Team photos and culture
✓ Technology stack and capabilities
✓ Portfolio by industry
✓ Regular contact form
✓ Blog / thought leadership
✓ Pricing or engagement model
✓ Careers section

Today: Explain the 6 reasons first (10 min), then open Lovable live and show participants how to create the /us-sled page inside their existing project. The demo takes 30–40 minutes. The impact lasts the entire program.

PART 2 - LIVE DEMO GUIDE

Lovable Live Demo - 8-Step Script

Follow each step in order. Estimated time: 40 minutes including questions. One participant volunteers their Lovable project for the live demonstration.

LIVE DEMO SESSION 40 min · Projector + Lovable.dev

Current site (before)→ Create /us-sled→ Paste 3 prompts→ Add navigation→ Before/After

Step-by-Step Demo Script

Open Lovable with the Participant’s Project

Open lovable.dev. Log in. Click the participant’s existing project to open the editor. The editor shows their current homepage on the right side of the screen.

If the participant has no Lovable project yet: create one fresh. Name it [CompanyName]-Main. This becomes the root project holding both the regular site and the SLED page.

Show the Current Site - The “Before” Moment

Display the participant’s current website on the projector. Ask the group: “If a Texas state procurement officer landed on this page right now, what would they think?” Let 2–3 participants answer before moving on.

Expected answers: “Looks like outsourcing” / “No government experience” / “No compliance badges”. These answers are correct. Use them to create the need before presenting the solution.

Create a New Route in Lovable - /us-sled

In the Lovable editor: open the Pages or Routes panel (left sidebar). Click Add Page. Name it us-sled. This becomes the URL /us-sled on their site, completely separate from the homepage.

In Lovable: Pages panel (left sidebar) → Add Page → name it “us-sled” → Create. You now have two pages: / (homepage) and /us-sled (SLED page).

Paste Prompt 1 - SLED Hero Section

Copy Prompt 1 from below. Fill in the participant’s company name, UEI, and NAICS code. Paste into the Lovable chat while on the /us-sled page. Watch the hero section appear in under 60 seconds.

This single prompt builds the complete above-the-fold section. Watch the room react when it appears. The transformation from a blank page to a professional US government landing page in 60 seconds is the most powerful moment of the session.

Paste Prompt 2 - Projects Section

Copy Prompt 2. Fill in the CollabP-assigned project details (South Platte Renew RFP 26-022 for web development companies). Paste into Lovable. The project card appears showing their first SLED case study.

For the live demo: use the actual project details from today’s assignment. Client: City of Englewood, Colorado. Project: Website Redesign and Development Services. Value: $250,000–$300,000.

Paste Prompt 3 - Dual Navigation

Copy Prompt 3. Paste into Lovable. This adds a “U.S. Government” button to the regular homepage that links to /us-sled, and a “Back to Main Site” link on the SLED page.

After this step: open the homepage and click the US Government button live. The audience watches the navigation switch between two completely different-feeling pages on the same site. This is the key demonstration moment.

Live Navigation Demo - Show Both Flows

Click through both pages live on the projector. Homepage → US Government button → SLED page. Then SLED page → Back to Main Site → homepage. Let participants see the two distinct experiences.

Say to the group: “Same company. Same Lovable project. Two pages. A US prime contractor clicks US Government and lands here. A Pakistani client lands on the regular homepage. Neither is confused. Both see exactly what they need.”

Before / After Screenshot - Share in Group Chat

Screenshot the original homepage (before). Screenshot the new /us-sled page (after). Put them side by side. Share in the War Room group chat.

Caption: “Same company. Two pages. Two audiences. Built this morning.”

The 3 Lovable Prompts

Fill in ALL bracketed fields with participant’s actual data before pasting. Generic prompts produce generic results. Specific inputs produce professional outputs.

Prompt 1 - US SLED Hero Section ▼

Prompt 2 - Projects and Prime Contractors Section ▼

Prompt 3 - Dual Navigation Connecting Both Pages ▼

PART 3 - CASE STUDY SYSTEM

CollabP Documents → Your Case Study

CollabP provides 3 documents per project: Summary of Procurement, Statement of Work, and Tender Insight. This guide shows exactly which section of each document feeds which section of the case study - and how to tailor it as your own company’s work.

The 3 CollabP Documents - What to Extract From Each

Summary of Procurement

Project overview, client details, location, scope summary, key objectives, evaluation criteria, contract duration, insurance requirements. Use for: Cover Block + The Challenge sections.

Statement of Work

Detailed scope (all Tasks 1–9), Deliverables Matrix, timeline, technical requirements, roles and responsibilities, payment milestones. Use for: Our Solution + Results sections.

Tender Insight

Strategic analysis, what the client really wanted, budget range intelligence, winning vs losing proposal behaviors, offshore framework. Use for: Executive Summary + Technologies sections.

Important: You MUST use real facts from the CollabP documents. Real client names, real contract values, real scope, real compliance requirements. You tailor the PRESENTATION (your company role, your team, your approach) but NOT the facts.

7 Required Case Study Sections

Cover Block - Project Identity

Source: Summary of Procurement. The who, what, where, when in one visual block.

Your Company Name *

Write as: [Company Name] - as Technology Subcontractor

Project Title *

Exact RFP title from Summary of Procurement

Client / Agency *

Full official name of the government agency

Contract Value *

From Tender Insight Section 13 Budget - state as range if not exact

Duration *

From SOW Section 2 Key Dates - contract start to estimated completion

CollabP Reference (optional)

RFP Number - e.g. RFP 26-022

Executive Summary - 4 Sentences Maximum

Source: Summary Section 1 + Tender Insight Section 2. Challenge, role, delivery, result.

The Challenge *

[Agency] needed to [problem]. The existing [system/process] was [specific failure from RFP background section].

Our Role *

[Company] was engaged as a technology subcontractor to deliver [responsibility] for [client].

What We Delivered *

We delivered [key deliverable] achieving [specific outcome with a number from the SOW performance standards].

The Result *

The project was completed [on schedule / X weeks ahead of schedule] and [measurable result].

The Challenge - Detailed

Source: Summary Section 1 (Project Overview) + Tender Insight Section 2 (Strategic Read). Describe the real problem the agency had.

Background *

Who is the client, what do they do, why did this project exist. 2–3 sentences. Use Section 1.3 of the RFP background.

Specific Problems *

3–4 bullet points. Use exact language from Summary Section 3 (Key Objectives) or SOW Section 4 (Buyer Requirements).

Key Technical Requirements *

List 3–4 most important requirements from SOW Section 8.1 (Mandatory Requirements). These are real and specific.

Why It Mattered (optional)

What was the consequence of not solving this? Citizens affected? Agency mission at risk?

Our Solution - What We Built

Source: SOW Section 5 (Scope of Work) Tasks 1–8. List each task you delivered. Write in your own words but keep the facts.

Our Approach *

How did your team approach this? What methodology? Discovery-first? Agile sprints? Describe your process.

Scope Delivered *

List each SOW Task you delivered. Personalize the language. Example: Task 2 “We designed wireframes and WCAG-compliant page templates for all interior page types...”

Your Team *

[X] specialists from [Company] led by [PM Name], including [roles]. List actual team structure.

Timeline *

Key milestones: kickoff → design approved → development complete → QA → launched. Use SOW Section 2 Key Dates.

Results & Outcomes - Numbers Only

Source: SOW Section 13 (Performance Standards). Each outcome must have a measurable number or percentage.

Primary Outcome *

WCAG 2.2 AA compliance achieved: zero Level A or AA failures at launch. (This comes from SOW Section 13 performance standard.)

Secondary Outcomes *

3–4 additional measurable outcomes. Example: Content migrated: 100% of existing pages. URL redirects implemented: zero broken links. Staff trained: [X] SPR staff members completed WordPress training.

Compliance Achieved *

WCAG 2.2 AA: compliant. Colorado accessibility law C.R.S. 24-85-101: compliant. VPAT: delivered within required timeframe.

Technologies & Compliance Frameworks

Source: SOW Section 8.1 (Mandatory Requirements) + Section 8.3 (Referenced Standards). List exact tools and frameworks.

Technology Stack *

From SOW Section 8.1: WordPress CMS, WCAG 2.2 AA compliant stack, translation integration (Google Translate API), advanced search tools, Leaflet or Mapbox for interactive mapping, Figma for design.

Compliance Frameworks *

From SOW Section 8.3: WCAG 2.2 Level A and AA, Colorado C.R.S. 24-85-101, VPAT (WCAG Edition), TABOR compliance awareness, IRCA I-9 compliance.

Testing Tools (optional)

axe DevTools Pro, WAVE API, Screaming Frog (content audit), cross-browser testing suite.

About Your Company - SLED Positioning

This is your SLED credentials statement, not a generic about section.

Company SLED Statement *

[Company] is a SAM.gov-registered IT services company (UEI: [UEI]) delivering technology solutions for U.S. state and local government agencies. Primary NAICS: [code].

Contact *

[Name] | Business Development | [US Phone] | [Email] | [SLED Page URL]

Portfolio Note (optional)

Additional U.S. state-level project references available upon written request.

Design Rules - What Participants Can and Cannot Do

✗ CANNOT DO

✗ Use CollabP’s document layout or format
✗ Change any numbers, outcomes, or client names
✗ Claim they were the prime contractor
✗ Redistribute the Tender Insight document
✗ Use CollabP’s logo or branding

✓ MUST DO

✓ Redesign with their own company branding
✓ Write in first person: We delivered...
✓ Add their SAM.gov UEI and NAICS code
✓ Include their company name and logo
✓ Describe their specific approach in their own words
✓ Link case study to their /us-sled page
✓ Save as PDF to Drive/05_Company_Credentials

South Platte Renew example: Title the case study “Website Redesign and Accessibility Compliance - City of Englewood, Colorado.” Role: WordPress development and WCAG compliance subcontractor. Value: $250,000–$300,000. Duration: 8 months. Technologies: WordPress, WCAG 2.2 AA, Figma, Leaflet, Google Translate API.

🔒 CollabP RSP Authorization Agreement

PDF with signature fields. Print and sign by hand, or annotate digitally in Adobe Acrobat, Preview, or any PDF viewer.

⬇ Download PDF

NDA FRAMEWORK

CollabP ↔ Company NDA - Making Project Use Official

Before any participant uses CollabP-assigned project data in case studies, websites, or proposals, they sign this agreement. It protects all parties and makes the case study use legally authorized.

Protects CollabP

>Prevents misrepresentation of proprietary research
>Prevents redistribution of Tender Insight analysis
>Maintains CollabP’s subscription service value

Protects the Participant

>Makes project data use officially authorized
>Protects from misrepresentation claims
>Written permission to reference project in proposals

Protects the Process

>Data used only for capability building
>No confidential client data shared externally
>Participant cannot contact the agency directly

Key NDA Provisions

1. Authorized Use: The Participant Company is granted a limited, non-exclusive, non-transferable license to use CollabP-provided project materials (Summary of Procurement, Statement of Work, Tender Insight) solely for creating portfolio case studies, capability statements, and proposal past performance sections. All other uses are prohibited.

2. Data Accuracy: Participant agrees to use only factual data from CollabP documents. Participant may not alter, fabricate, or misrepresent client names, contract values, project scope, outcomes, timelines, or compliance requirements. Tailoring is permitted only for the Participant’s own role and team description.

3. Role Representation: Participant must accurately represent their role as a subcontractor or service provider - not as the prime contractor - unless explicitly confirmed otherwise by CollabP in writing.

4. Confidentiality of Tender Insight: The Tender Insight document contains CollabP’s proprietary strategic analysis and is classified confidential. Participant may use the intelligence contained therein but may not reproduce, redistribute, or share the Tender Insight document with any third party.

5. Permitted Publications: Participant may publish derived case studies on their company website, in proposals to US government agencies, in capability booklets, and in professional profiles. Participant must not claim CollabP’s authorship in any public-facing document.

6. Non-Compete on CollabP Services: Participant may not use CollabP materials to compete with CollabP’s own services or resell CollabP’s analysis to other companies.

7. Term: Effective from date of signing and remains in force for the duration of the Participant’s War Room membership and for two (2) years thereafter.

8. Governing Law: Disputes resolved through mutual written agreement between the parties.

Signing process today: distribute NDA before assigning the project → each company principal signs → CollabP counter-signs → both keep a copy → only then hand over the 3 project documents. Takes 10 minutes total for all participants.

FULL DAY 24 GUIDE

War Room 3 Complete Session Plan - All Topics and Timings

Complete guide covering all three parts: dual-site strategy, live Lovable demo, and case study conversion. Every session block is mapped with timing and what to cover.

Full Day Schedule - Sunwar room 3 May 2026

Time	Session Block	What Happens
9:00–9:30	Opening: The Dual-Site Strategy	Explain the 6 reasons for the dual-site strategy (Part 1). Show the visual comparison. Ask participants: “If a Virginia DOT officer landed on your site right now, what would they think?”
9:30–10:30	Live Lovable Demo	Follow the 8-step demo script from Part 2. Create the /us-sled page live. Paste the 3 prompts. Show dual navigation. Before/After screenshot. Group discussion.
10:30–11:00	NDA Signing + Project Assignment	Distribute and sign the CollabP NDA. Hand over the 3 project documents. Assign sector based on company specialization. Web development companies: South Platte Renew RFP 26-022.
11:00–11:15	Break	-
11:15–12:00	Case Study Walkthrough	Walk through the 7-section case study template from Part 3. Show exactly where each piece of data comes from in the 3 CollabP documents. Demonstrate with South Platte Renew example.
12:00–13:00	Lunch	-
13:00–15:00	Participants Write Case Studies	Each company writes their case study using the 7-section template and their assigned project data. Check: first person writing? Numbers from CollabP documents? Company name and UEI included?
15:00–16:00	US SLED Page Building	Each company opens Lovable and builds their /us-sled page using the 3 prompts. They fill in their own company details, add the case study project card, and connect the dual navigation.
16:00–16:45	Service-to-SLED Mapping	Walk through the US positioning language table. Each company maps their services to US government procurement language and adds these to their /us-sled services section.
16:45–17:30	Submission and Group Review	Every company submits: /us-sled URL, case study PDF, before/after screenshots. Group reviews 2–3 sites live.

Service-to-SLED Mapping Table

Every participant’s services must be described in SLED language on the /us-sled page. Use this table to translate technical services into US government procurement language.

Your Service	SLED Language for US Page	NAICS	Typical Client
WordPress Development	Government Web Portal Design & Development - WCAG 2.2 AA Compliant	541511	State agencies, municipalities, utilities
Mobile App Development	Citizen-Facing Mobile Application Development for Government Service Delivery	541511	State DOTs, Health Depts, Education Agencies
Cybersecurity	NIST 800-53 / CJIS / CMMC Compliance and Security Operations	541519	Law enforcement, courts, state agencies
Cloud / DevOps	FedRAMP-Aware Cloud Migration and Infrastructure for Government Systems	541512	State IT offices, DOTs, utilities
Data Analytics	Government Performance Dashboard and Business Intelligence Solutions	541511	Public health, transportation, education
IT Managed Services	24/7 Government IT Help Desk and End-User Support - ITSM	541513	County governments, municipalities
UI/UX Design	Accessible, WCAG-Compliant User Experience Design for Public Sector	541430	Any government digital transformation
QA Testing	Formal Accessibility Auditing and Software Quality Assurance for Government	541519	Any government digital project

War Room 3 Deliverables - Every Company Must Submit

#	Deliverable	Description	Format
1	NDA Signed	CollabP - Company NDA signed and filed with both parties	Signed document
2	Case Study - 7 Sections	Written using CollabP data, company’s own branding and layout	PDF
3	/us-sled Page Live	Built in Lovable, publicly accessible URL shared in group chat	Live URL
4	Dual Navigation Working	Homepage links to SLED page and SLED page links back	Live URL
5	Before / After Screenshots	Original homepage and new /us-sled page side by side	Screenshot
6	Case Study Saved to Drive	PDF in Drive/05_Company_Credentials folder	PDF in Drive