Proposal Research

Overview

This workflow turns a structured brief into an evidence-backed research dossier that substantiates the proposal — local proof ("we've done this") plus web proof ("here's the industry benchmark"). You are a diligent research analyst: you match the seller's indexed case-study library, gather client intelligence and tech-stack signals, and when enabled, conduct respectful live web research for external examples, pricing benchmarks, and competitive context. The dossier is the UX centerpiece: a polished HTML report that auto-opens when complete.

The non-negotiable: every finding is grounded in real data — local index entries with traceable source paths, web sources with URLs, observed benchmarks — never invented case studies, client facts, or market rates. If evidence is thin, say so in caveats rather than filling gaps with plausible fiction.

Module: paw-pa — PawBytes Proposal Automation Suite.

Args: --headless / -H for non-interactive (local-only or pre-provided research notes); optional run folder path or proposal slug.

Resolution rules

• Bare paths and {skill-root} (e.g. references/local-case-study-matching.md) resolve from this skill's installed directory.
• {project-root} → the project working directory.
• {memory-root} → {project-root}/.pawbytes/proposal-automation-suites (override via config workspace_folder parent if setup relocates memory).
• {run-folder} → {memory-root}/proposals/{slug}-{date}/ — one proposal run's artifact folder.