How to get your first AI client this week

Everything you need to go from reading the issue to booked on a call with a real potential client. This version includes the full GitHub setup and the missing project files from the May issue, expanded in Section 1.

Section 1 — Get Your Demo Live on Render

You already built the AI dashboard insights project back in May. It's sitting on your machine, unseen by anyone. Here's how to put it online — the complete version, including the GitHub steps and the two files the original issue skipped.

Step 1 — Push your project to GitHub (the full version)

1. Create a GitHub account at github.com if you don't already have one.
2. Create a new repository. Click New → give it a name (e.g. ai-dashboard-insights) → keep it private if the code has client data in it.
3. Push your local project to that repo. From your project folder:

git init
git add .
git commit -m "initial commit"
git branch -M main
git remote add origin <https://github.com/your-username/ai-dashboard-insights.git>
git push -u origin main

1. Connect the repo to Render in the next step below. Every future update deploys automatically — once connected, any git push to main triggers a new deploy. No manual uploads, ever again.

Step 2 — The two files the May issue didn't show

If you're working from the May Render Workflows tutorial (fetchData.ts, analyzeData.ts, sendReport.ts, workflow.ts), you also need these two files. They weren't shown in that issue but are required for the project to run.

index.ts — the entry point. It imports your wired-up workflow and runs it. Nothing more.

import { runWorkflow } from './workflow'

runWorkflow()

package.json — defines the project, its scripts, and its dependencies.

{
  "name": "ai-insights-workflow",
  "version": "1.0.0",
  "type": "module",
  "main": "index.js",
  "scripts": {
    "build": "tsc",
    "start": "node dist/index.js"
  },
  "dependencies": {
    "@renderinc/sdk": "latest",
    "node-fetch": "^3.3.2"
  },
  "devDependencies": {
    "typescript": "^5.4.0",
    "@types/node": "^20.11.0"
  }
}

tsconfig.json — since the project is TypeScript, this tells the compiler how to turn your .ts files into runnable JavaScript.

{
  "compilerOptions": {
    "target": "ES2022",
    "module": "ESNext",
    "moduleResolution": "Node",
    "outDir": "dist",
    "rootDir": ".",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true
  },
  "include": ["**/*.ts"],
  "exclude": ["node_modules", "dist"]
}

Your finished folder should look like this: