Ready. SETT. Go. — Wade's Setup Guide

What You're Getting

Four live sites, one access key, one Git repo. Here's the full picture.

One Key For Everything

gunga-gu-lunga

Client-Facing

Ready. SETT. Go. — Pitch Deck

https://racetrac-client.pages.dev

The one you send to RaceTrac. Kelly Tech branding. Heritage story, capabilities, Fuel Intelligence Hub, shared values, Ask Carl AI demo. Links to the full RFP response at the end.

Client-Facing

Full RFP Response

https://racetrac-response.pages.dev

Wade's full proposal converted into a navigable web experience. 13 sections — Executive Summary through Compliance Matrix. Expandable accordions, SLA table, domain coverage grid. Right-side nav with section tracking.

Internal Only

Ready. SETT. Go. — Internal Version

https://ready-sett-go.pages.dev

Same pitch deck but with internal strategy analysis, Shetty intel, proposal gap notes, and the compliance matrix. Includes "View the Strategy" and "View the Technical Response" hidden sections. Don't send this to RaceTrac.

Internal Only

RFP Collaboration Portal

https://rfp-portal.pages.dev

Internal war room. Research docs, fuel domain drafts, action items, checklists. The workspace where the response was coordinated.

Repo Structure

The Git repo contains all source files, research docs, and deployed site assets.

kelly-sett/
├── racetrac-client/ — Client-facing pitch deck (Kelly Tech branding)
│ └── index.html, favicon.png, _headers, robots.txt
├── racetrac-response/ — Full RFP response web experience
│ └── index.html, favicon.png, _headers, robots.txt
├── ready-sett-go/ — Internal pitch deck (with strategy/intel)
│ ├── index.html — Main site
│ ├── THE-CARL-STANDARD.md — Carl Standard research
│ ├── THE-FULL-NARRATIVE.md — Complete narrative doc
│ └── COMPETITIVE-GIVING-RESEARCH.md
├── leads/RaceTrac/ — All RaceTrac research and source docs
│ ├── RaceTrac RFP and Response Docs/ — Wade's original docs
│ │ ├── Motion Docs/ — Proposal, AI response, compliance matrix
│ │ └── RaceTrac Docs/ — Original RFP, Exhibit A/B, Workshop slides
│ ├── rfp-portal/ — Collaboration portal source
│ ├── AMEET-SHETTY-DEEP-INTEL.md
│ ├── RACETRAC-RFP-GAP-ANALYSIS.md
│ └── WIN-STRATEGY.md
├── DEPLOYED-SITES.md — All URLs and access keys
├── RICHARDS-CHEATSHEET.md — Presentation talking points
└── EMAIL-DRAFT.md — Email template for team

Setup Instructions

Everything runs on Node.js with Cloudflare Pages for hosting. Here's how to get set up from scratch.

1

Install Node.js

Recommended: use nvm (Node Version Manager) to manage Node versions.

# Install nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.0/install.sh | bash

# Restart terminal, then install Node
nvm install 24
nvm use 24

# Verify
node --version # should be v24.x
npm --version # should be 11.x

2

Install Pi (AI Coding Agent)

Pi is the AI agent that built all of this. It runs in your terminal and can read, write, edit files, run commands, search the web, and deploy to Cloudflare.

npm install -g @mariozechner/pi-coding-agent

# Required extensions for web search, subagents, etc.
npm install -g pi-web-access
npm install -g pi-subagents

# Verify
pi --version

You'll need an Anthropic API key. Pi will prompt you on first run, or you can set it:

export ANTHROPIC_API_KEY=your-key-here

3

Install Wrangler (Cloudflare CLI)

Used to deploy sites to Cloudflare Pages.

npm install -g wrangler

# Login to Cloudflare (one-time)
wrangler login

4

Clone the Repo

git clone <repo-url> kelly-sett
cd kelly-sett

Making Changes & Deploying

Each site is a folder with an index.html. Edit the file, deploy, done.

Deploy a site

# From the site's directory
cd racetrac-client
npx wrangler pages deploy . --project-name=racetrac-client

# Other sites:
cd racetrac-response
npx wrangler pages deploy . --project-name=racetrac-response

cd ready-sett-go
npx wrangler pages deploy . --project-name=ready-sett-go

cd leads/RaceTrac/rfp-portal
npx wrangler pages deploy . --project-name=rfp-portal

Commit changes

git add -A
git commit -m "Description of what changed"
git push

After deploying

Cloudflare caches aggressively. Tell anyone viewing the site to hard-refresh: Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows).

Using Pi

Pi is the AI coding agent that built everything in this project. It runs in your terminal and works like having a senior developer next to you who can read files, write code, run commands, search the web, and deploy — all through conversation.

Start Pi

# Navigate to the project
cd ~/Projects/kelly-sett

# Launch Pi
pi

Example prompts

# Edit content
"Change the subtitle on the client pitch deck to say XYZ"

# Add a section
"Add a new slide about our ServiceNow capabilities after the Fuel Edge slide"

# Deploy
"Deploy the client pitch deck to Cloudflare"

# Research
"Research DaySmart's technology stack and build a pitch deck for them"

# Fix issues
"The text on the fuel section is hard to read on mobile, fix it"

# Create new assets
"Create a new client-facing site for [prospect] using the same design system"

How Pi works

Pi reads your files, understands the codebase, and makes precise edits. It doesn't guess — it reads the actual HTML, finds the exact text, and replaces it. If it needs to deploy, it runs the Cloudflare CLI. If it needs research, it searches the web.

Think of it as a conversation with a developer who already knows the project. Tell it what you want in plain English. It handles the rest.

Tips

Be specific. "Make the hero text bigger" works. "Make it look better" doesn't.

Reference sections. "On the Fuel Edge slide" or "in the closing section" helps Pi find the right place.

Ask it to deploy. Pi can deploy directly — just say "deploy it."

Start fresh sessions. If Pi seems stuck or slow, start a new session. Context windows have limits.

A SETT of Instructions