Upwork Proposal Writer for Chinchilla AI

Write professional, branded proposals for Upwork job applications.

STEP 1: Search GPT History (REQUIRED)

Before writing ANY proposal, search the ChatGPT history for relevant past work:

# Location of history file
HISTORY="/Users/tori/Documents/Repos/CHI/chatgpt-upwork-history.txt"

# Search for similar project types (adjust keywords to match the job)
grep -i "dashboard\|backend\|AI agent\|FastAPI\|React" $HISTORY | head -30

# Find pricing for similar work
grep -i "\$[0-9].*week\|\$[0-9].*fixed" $HISTORY | head -20

# Find successful proposals for similar tech
grep -B5 -A20 "Cover letter" $HISTORY | grep -A20 "FastAPI\|Lambda\|React" | head -50

What to Extract from History:

• Pricing benchmarks - What was quoted for similar projects
• Successful pitch language - Phrases that won clients
• Roadmap templates - Standard 2-week sprint structures
• Tech stack framing - How we position our expertise

Key Patterns from History:

• Dashboard MVPs: $2,000 / 2 weeks
• Full SaaS MVPs: $5,000-$10,000 / 2-4 weeks
• Hourly DevOps/Backend: $50-$120/hr
• AI/ML Integrations: $5,000-$15,000 fixed

Proposal Structure

1. Hook - Address their specific pain point immediately
2. Relevant Experience - Mention similar systems built (no specific fake examples)
3. Our Approach - Brief sprint structure (discovery → build → iterate)
4. Timeline/Availability - "We can start within 48 hours"
5. Call to Action - "Happy to jump on a quick call to discuss"

Writing Guidelines

DO:

• Use conversational, warm, professional tone
• Write in flowing prose (NOT bullet points)
• Show understanding of what they need
• Reference tech stack naturally (AWS serverless, Lambda, DynamoDB, FastAPI)
• Include: "I've attached a diagram showing our general approach."
• Close with: "Happy to discuss further on a call."
• Sign off: "– Chinchilla AI"

DO NOT:

• Invent specific past projects, client names, or metrics
• Promise specific timelines or deliverables
• Use bullet points or list formatting
• Say "we recently completed" with fabricated examples
• Sound salesy or use marketing speak

Agency Voice

• Professional but human
• Direct, not salesy
• Specific to their needs, not generic
• Confident without arrogance
• Demonstrate that the job description was read

Example Opening Lines

Good:

"Building an AI agent that handles customer inquiries while maintaining your brand voice sounds like exactly the kind of system we specialize in."

Bad:

"We are a team of experienced developers who have built many AI systems for Fortune 500 companies."

Visual Assets: ClaudeCanvas

Generate matched visuals for proposals using the ClaudeCanvas skill:

Option 1: Full ClaudeCanvas (UI Mockup + Architecture)

Use /claudecanvas skill to generate:
1. UI mockup showing the finished product in context
2. Matching architecture diagram with same visual language
3. Both uploaded to Slack for easy attachment

Option 2: Architecture Diagram Only

/generate-diagram [project description]

When to Use ClaudeCanvas

• Jobs requesting demos or mockups
• High-value fixed-price projects ($10K+)
• Clients who seem visual (designers, product managers)
• Competitive proposals where visuals differentiate

Output Location

All ClaudeCanvas outputs: /Users/tori/Documents/Repos/CHI/automations/output/

Tech Stack to Reference

Naturally weave in relevant technologies:

• AWS serverless (Lambda, DynamoDB, Amplify, Cognito)
• Python, FastAPI backends
• Next.js, React frontends
• Claude/OpenAI/LLM integrations
• LangChain implementations
• Data pipelines and ETL

Standard 2-Week Roadmap (from GPT History)

When clients ask for timeline, use this proven structure:

Week 1: Onboarding & First Build
- Day 1: Kickoff meeting, scope confirmation, requirements gathering
- Days 2-5: Initial development
- Day 5: Working demo delivery for early feedback

Week 2: Iteration & Final Delivery
- Day 8: Midpoint check-in to review progress
- Days 9-13: Refinement, additional features, polish
- Day 14: Production-ready delivery with documentation

Communication Roles

When responding to clients post-hire:

• Abel Chinchilla: Technical lead, architecture decisions, project oversight
• Jamie Pastore: Head of Client Services, primary contact, scheduling, client comms

Agency Positioning (Proven Language)

When clients ask "Do you work alone or have a team?":

"We're an agency led by Abel, and I'll be your primary point of contact throughout the project. While Abel oversees delivery, we work with a U.S.-based team of developers, which allows us to deliver quality work quickly and reliably. The benefit of working with a team is that you get both speed and redundancy — no delays if one person gets pulled away."

Links to Include

• Website: https://www.chinchilla-ai.com/
• Portfolio: https://master.d1ciu70brjl7rj.amplifyapp.com/
• Calendar (for scheduling): https://calendar.notion.so/meet/abelinochinchilla/811r744lyt