Internal Document

JobSeam Marketing
Launch Playbook

What each marketing file does, where and how to publish it, whether you need hosting, and a day-by-day execution plan from pre-launch to first paying customer.

Version 1.0 Updated July 2026 Audience Founder / Founding team Folder jobseam-marketing/
Contents
  1. 1. What each file is
  2. 2. Do you need hosting?
  3. 3. Where and how to publish
  4. 4. How to use each material
  5. 5. Day-by-day 30-day plan
  6. 6. When to host the platform itself
Section 1

What each file is

Five HTML files and one PPTX in the jobseam-marketing/ folder. All HTML files are fully self-contained — screenshots, styles, and scripts are embedded — so they open in any browser with no server, no internet connection, and no dependencies.

File What it is Format Size Audience
jobseam-onepager.html Single-page sales overview. Features, ROI strip, multi-context comparison with live screenshots. First thing a cold prospect should see. HTML ~340 KB Cold prospects, warm intros
jobseam-deck.html 12-slide pitch deck in the browser. Problem, solution, platform features, market, traction, ask. For investor meetings and deep-dive prospect calls. HTML ~46 KB Investors, serious prospects
jobseam-deck.pptx Same deck as PowerPoint. Use for live screen-share presentations when you need slide control, or to email as an attachment. PPTX ~2 MB Live presentations
jobseam-video.html Full-screen animated player (19 scenes, auto-advance) + complete annotated walkthrough below. Every role, every feature, live screenshots. Your best "see it in action" link. HTML ~6 MB Anyone who wants to see the product
jobseam-feature-guide-detailed.html Complete feature reference: every filter, every column, every setting. Side-by-side screenshots of consulting vs. university context. For technical buyers who want to vet before committing to a demo. HTML ~350 KB Technical buyers, power users
jobseam-go-to-market.html Internal playbook: 30-day content calendar, YouTube script, channel tactics, outreach messaging. Not for prospects — this is your execution plan. Reference it daily. Internal ~54 KB Founder only (internal)
One rule for sharing
Never send all five files at once. Each material has a specific moment in the sales sequence. Sending everything upfront overwhelms prospects and removes your reason to follow up. See Section 4 for when to send what.
Section 2

Do you need dedicated hosting?

Short answer: no, not yet. The long answer depends on what you're hosting — the marketing pages are a completely different question from the product platform.

Marketing materials (the HTML files)
These are 100% static files. No database, no backend, no server process. A $0 GitHub Pages deployment gives you a permanent public URL in under 5 minutes. A VPS would be pure waste for this.
The JobSeam platform (for demos)
Currently running on Docker at localhost. For screen-share demos — Zoom, Google Meet — this is exactly right. You control the data, the environment, and the flow. No public access needed until you're ready to send "try it yourself" links.
The decision rule
Get to your first 3 paying customers with screen-share demos and static marketing pages. Then spend $6/month on a VPS (DigitalOcean, Hetzner) to run a live demo instance publicly. Custom domain costs $12/year. Nothing else is needed in year one.

Hosting options for the marketing pages

Netlify Drop
Free
Drag the jobseam-marketing/ folder onto netlify.com/drop. Get a URL in 30 seconds. No account required for a quick share. Good for one-off sending before GitHub Pages is set up.
Cloudflare Pages
Free
Connect your GitHub repo. Auto-deploys every time you push. Best CDN performance globally. Good choice if you expect international prospects early.
Custom Domain
Buy jobseam.io (or .com) from Namecheap or Cloudflare Registrar. Point it to GitHub Pages. Subdomains like demo.jobseam.io and deck.jobseam.io are free once you own the domain.
Section 3

Where and how to publish each file

Step-by-step: getting URLs for every file using GitHub Pages. Do this once — then every update is a git push.

One-time setup: GitHub Pages

1
Create a GitHub repository. Go to github.com, create a new repo named jobseam-marketing. Set it to Public (required for free GitHub Pages).
2
Push the marketing folder. In your terminal:
cd /Users/jshaik/quezaal/jobseam-marketing
git init && git add *.html *.pdf *.pptx
git commit -m "Initial marketing materials"
git remote add origin https://github.com/jilani20/jobseam-marketing.git
git push -u origin main
3
Enable GitHub Pages. In the repo → Settings → Pages → Source: Deploy from a branch → Branch: main → folder: / (root). Click Save. Pages deploys in ~60 seconds.
4
Your URLs are live. Every file in the repo gets a URL at:
https://jilani20.github.io/jobseam-marketing/[filename].html
Save each URL — these are your shareable links for every campaign.
5
Optional: custom domain. In Pages settings, add marketing.jobseam.io or similar. Add a CNAME record at your DNS provider pointing to jilani20.github.io. Takes about 10 minutes. From then on, every file is at https://marketing.jobseam.io/[filename].html.

Per-file publishing summary

File Publish as Primary share method Do NOT
jobseam-onepager.html GitHub Pages URL
/jobseam-onepager.html
Link in LinkedIn DMs, link in cold outreach email, pin to LinkedIn profile Attach as a file — prospects won't open .html attachments
jobseam-video.html GitHub Pages URL
/jobseam-video.html
LinkedIn post CTA, YouTube description, post-demo follow-up email Send as first contact — too much. Save it for warm leads.
jobseam-deck.html GitHub Pages URL
/jobseam-deck.html
Share link with investors; send after a discovery call when prospect asks "can you send something?" Use for live screen-share — use the PPTX instead
jobseam-deck.pptx Google Drive or Dropbox
(not GitHub — binary file)
Open in PowerPoint/Keynote for live Zoom presentations. Share Drive link if they ask for slides. Email as attachment — too large for most inboxes
jobseam-feature-guide-detailed.html GitHub Pages URL
/jobseam-feature-guide-detailed.html
Send to prospects who ask technical questions, or after an intro call to close a demo Send cold — overwhelming for first contact
jobseam-go-to-market.html Local only — do not publish Open in your browser, reference daily. Contains your outreach strategy. Publish publicly — this is an internal strategy document
Section 4

How to use each material

Each file has a specific role in a specific moment of the funnel. Using the wrong material at the wrong moment either under-informs or overwhelms.

One-Pager
jobseam-onepager.html
Your broadest-reach asset. It answers "what does this do?" in under two minutes of reading. Use it as the first link you share with anyone — cold or warm. It has enough to create curiosity, not so much that it replaces a conversation.
When to send
Cold DMs, cold emails, LinkedIn post CTAs, after someone asks "what is this?"
What you say
"Here's a quick overview of what we've built: [link]. Happy to walk through it live if relevant."
Goal
Get a reply. Get them to book a demo. Not to close.
Video Walkthrough
jobseam-video.html
The highest-converting single asset you have. The full-screen player auto-plays and walks through the real product in 19 scenes with narration. The detailed annotated walkthrough below it covers every feature, every role, and every group context with actual screenshots. Send this when someone says "I'd like to see it before booking a call."
When to send
After initial interest, as YouTube description link, in post-demo follow-up, in LinkedIn posts as "watch it in action"
What you say
"Full platform walkthrough here — the player at the top auto-plays. Scroll down for annotated detail on every feature."
Goal
Self-serve demo. Book a live call for the 30% who want to talk after watching.
Pitch Deck (HTML)
jobseam-deck.html
Use the HTML version for async sharing — investors, advisors, and warm intros who want to review at their own pace. It loads in a browser and works on any device. The narrative arc is: problem → why now → solution → platform → market → traction → ask.
When to send
Investor intros, after discovery calls when prospect asks to share with their team, warm referrals
What you say
"Deck is here: [link]. Opens in a browser, no download needed."
Goal
Fundraise conversations. Warm up referrals who will forward to a prospect.
Pitch Deck (PPTX)
jobseam-deck.pptx
Use this for live presentations. Open in PowerPoint or Keynote before the call, share screen, and present slide-by-slide. You control the pace, you can skip slides based on the conversation, and you can add live annotations.
When to use
Zoom investor calls, in-person demo meetings, conference presentations
Tip
Keep slides 8–12 (platform features) ready but skip to what's relevant. Don't force all 12 in 30 minutes.
Goal
Drive to the "can I try it?" or "what does a pilot look like?" question by slide 10.
Feature Guide
jobseam-feature-guide-detailed.html
Your technical close asset. Send it after an intro call when someone says "I want to understand exactly what filters exist" or "how does the matching actually work?" It has the full filter list, every column, 2FA, AI pipeline details, and side-by-side screenshots from consulting vs. university contexts.
When to send
After discovery call, when prospect is evaluating seriously, to technical co-founder / CTO at a potential customer
What you say
"Full feature reference here — covers every filter, column, AI pipeline, 2FA, and group context. Let me know if anything is missing for your evaluation."
Goal
Remove objections before they become blockers. Answer "does it do X?" before it's asked.
The share sequence
Cold outreach → One-Pager link. They reply with interest → book a call. Pre-call → Video link. On call, share screen → PPTX deck. Post-call follow-up → Feature Guide if they're evaluating. Investor intro → HTML deck async.
Section 5

Day-by-day 30-day launch plan

This maps directly to the content calendar in jobseam-go-to-market.html, but adds the marketing materials, hosting steps, and outreach cadence in one view. The goal by day 30: at least 3 active demo conversations and 1 signed pilot or paid trial.

Activity types
Setup One-time infra tasks   Publish Put something live   Content LinkedIn / YouTube posts   Outreach Direct messages / emails   Demo Live product sessions   Video Record / upload
Pre-Launch (Before Day 1)
P–3
Setup Create GitHub repo jobseam-marketing. Push all HTML files. Enable GitHub Pages. Save all live URLs.
Setup Buy a domain if you don't have one (jobseam.io, ~$12). Point it to GitHub Pages.
P–2
Video Record the YouTube walkthrough using the script in jobseam-go-to-market.html. Don't over-produce. One good take, screen capture, USB mic.
Setup Build your LinkedIn prospect list: 150 IT staffing owners (Sales Navigator: 11-200 employees, VP/Owner/Director title). Save to spreadsheet.
P–1
Setup Upload YouTube video. Set title: "JobSeam: AI-powered bench sales platform demo." Add one-pager URL and video walkthrough URL to description.
Setup Update your LinkedIn profile: headline mentions JobSeam + AI talent matching. Featured section: pin one-pager URL.
Week 1 · Days 1–7 · Announce + First Wave
Day 1
Publish Post LinkedIn launch announcement. Pain-first: "We built JobSeam because bench sales teams lose real time every day reading vendor emails…" (avoid stating a specific hours figure unless you can back it). Link to one-pager. Pin to profile.
Content Share the YouTube video on LinkedIn as a second post (or the same day, a few hours later): "Watch the full platform walkthrough."
Day 2
Outreach LinkedIn DM Wave 1: send to 50 prospects from your list. Message 1: empathy + insight, no pitch. "Running into this specific pain?" Not "check out my product."
Day 3
Outreach Join 5 bench sales WhatsApp groups or Facebook groups. Introduce yourself as someone building staffing tools. No pitch. Just presence.
Content Respond to every LinkedIn comment on the Day 1 post. Algorithm rewards engagement in the first 24–48 hours.
Day 4
Content Post: "What if you walked in to this" — screenshot of the Match page with scored consultants. Real numbers. No sales copy. Let the product speak.
Outreach Follow up with anyone who replied to Wave 1 DMs. Offer the one-pager link or book a 20-min demo directly.
Day 5
Outreach LinkedIn DM Wave 1 follow-up: message 2 to those who opened but didn't reply. More specific — reference their firm size or market.
Day 6
Content Thought leadership post: "Hot take — the bench sales bottleneck isn't sourcing, it's matching speed." Engage replies for 48 hours. Follower growth driver.
Day 7
Setup Week 1 review. Which post got the most views? Which DM message got replies? Adjust Wave 2 message template based on what worked. Update your prospect spreadsheet with status.
Week 2 · Days 8–14 · Content + Demos
Day 8
Content Post: "Candidate-angle" — talk to the consultant, not the firm. "Your recruiter's job is easier with better tools." Reaches a broader audience who will share with their employer.
Day 9
Outreach LinkedIn DM Wave 2: 50 new prospects. Adjust message based on Week 1 learnings. Target bench sales managers this wave (different angle from firm owners).
Video Record Video 2: live demo format. Pick a real vendor email, paste it into Req Inbox, show the AI extraction, run a match. No script — just the product working.
Day 10
Demo Run demo sessions with anyone who replied from Wave 1. Use PPTX deck for first 5 slides, then switch to live product on localhost. Share video walkthrough link after.
Day 11
Publish Upload Video 2 to YouTube. Share on LinkedIn with "requested by several people who wanted to see the AI extraction live" framing.
Outreach Follow up with demo attendees. Send feature guide link to anyone who asked technical questions.
Day 12
Content University angle post: "We run the same platform for universities placing CS graduates. Same match engine. Different labels." Share the comparison screenshots from the video walkthrough.
Day 13
Outreach Wave 2 follow-up: message 2 to those who haven't replied. More specific insight. Offer the video link directly ("here's a 5-minute watch before we book time").
Outreach Start university outreach: 20 career services department heads at mid-size universities. Separate message track — lead with "placement-readiness" not "bench sales."
Day 14
Setup Week 2 review. How many demos ran? What objections came up? Update the pitch to address the top 2 objections before they surface next time. Note which materials people actually opened.
Week 3 · Days 15–21 · Proof Points + Scale
Day 15
Content "What we've seen in the data" post. Use real numbers from the live system: 22,000+ jobs indexed, N sources, average match time. Market data earns trust.
Demo Run demo batch 2 — university prospects from Day 13 outreach + anyone new from Wave 2.
Day 16
Outreach Wave 3: 50 new staffing firm prospects. This wave: target people who commented on industry posts (they're engaged, they're online now). Connection request + note, then DM if they accept.
Day 17
Content Individual user angle post: "You don't have to be a staffing firm to use this. If you're a consultant managing your own job search, there's a solo tier." Link to one-pager.
Day 18
Video Record Video 3: university context. Show the Students page, the cohort view, the placement-readiness breakdown. Fresh angle for a different audience.
Outreach Post-demo follow-up to Week 2 demos. "Any questions after reviewing? Happy to do a technical deep-dive if that helps." Offer feature guide link.
Day 19
Publish Upload Video 3 to YouTube. Share with the university audience specifically.
Demo First pilot conversation: for any prospect who attended 2 demos and asked detailed questions, move to "what does a 30-day paid pilot look like?" No free trials — a paid pilot validates intent.
Day 20
Outreach Community engagement: post something genuinely useful in the bench sales WhatsApp/Facebook groups. Answer a question someone asked. Build credibility before pitching in communities.
Day 21
Setup Week 3 review. Which channel drove the best conversations — LinkedIn content, direct DMs, communities? Double the best one in Week 4. Drop the worst one entirely.
Week 4 · Days 22–30 · Convert + Commit
Day 22
Content Post the content type that got the highest engagement in Weeks 1–3. Repeat the format, not the topic.
Outreach Warm leads re-engagement: anyone who opened a link, watched the video, or replied but went quiet. One more touch, with a new angle or data point.
Day 23–25
Demo Run all pending demo sessions. For each one: lead with the pain they described, not the product. Show the specific feature that solves their specific problem. Ask for pilot commitment at end.
Day 26–28
Outreach Wave 4 outreach based entirely on what worked. Same prospect profile as your best Wave 1–3 responses. Message based on what language got replies.
Content 2–3 more posts based on highest-engagement format from previous weeks.
Day 29–30
Setup 30-day retrospective. How many demos? How many pilots proposed? How many paying? Which marketing material was referenced most in conversations? Use this to plan Month 2.
Setup If you have even 1 paying pilot: write a one-sentence description of exactly who they are and what made them convert. That's your ICP. Build everything in Month 2 around finding more of them.
Section 6

When to host the platform itself

The marketing files are solved by GitHub Pages. The JobSeam platform — the Docker stack running at localhost — is a separate question. Here's how to think about it.

Stage Demo method Hosting needed Cost
First 0–10 demos Screen-share (Zoom, Meet). You run the app locally, share your screen. You control everything. None. Localhost is ideal — real data, full control, instant reset. $0
Prospects ask to try it themselves Self-serve trial access. They need a URL they can open independently. VPS with Docker. Deploy the full stack. One server, one environment. $6–$12/mo (DigitalOcean, Hetzner)
Multiple pilots running concurrently Each customer needs their own group and data isolation. Same VPS works for 3–5 groups. Add more resources when needed. Still no dedicated infra required. $12–$24/mo
First paying tier Production environment. Customers expect uptime and backups. Two servers: app + database, or managed Postgres (Supabase/Neon). Set up backups. Add SSL certificate (free with Let's Encrypt). $20–$40/mo
Recommended path for the platform

When your first prospect says "can I log in and try it myself?" — that's the trigger. Not before. Set up a $6/mo DigitalOcean droplet, deploy the Docker Compose stack, add a free SSL cert with Certbot, create a demo group for them. Total setup time: 2–3 hours.

Use Hetzner (€3.79/mo) if cost matters more than location. Use Railway or Render if you want the platform managed (no SSH required, ~$20/mo). Railway in particular supports Docker Compose and deploys from GitHub.

Don't do this before you need it
Setting up hosted infrastructure before you have a prospect asking for self-serve access is a distraction. Every hour spent on DevOps is an hour not spent on the 3 conversations that could get you your first paying customer. Screen-share demos close deals. Perfect uptime does not.

Quick-reference: what to set up and when

JobSeam Marketing Playbook  ·  Internal use only Updated July 2026  ·  jobseam-launch-guide.html