# Engineering-as-Marketing Knowledge Base

Public tools, calculators, widgets, directories, scorecards, templates, and conversion assets that create practical demand by helping users solve a real problem.

## Purpose

This knowledge base helps operators turn ideas into useful public tools and static assets that attract, qualify, educate, or convert users.

Use this folder to support:

- Public calculators
- Readiness scorecards
- Static widgets
- Interactive prompt generators
- AI tool directories
- Funding comparison tools
- Partner resource generators
- Lead magnet pages
- SEO-driven tools
- Static Vercel apps
- Custom GPT launch pages

## Primary Users

- AI product builders
- Static site builders
- Vercel app builders
- Funding operators
- Affiliate operators
- Content marketers
- SEO builders
- Partner managers
- Agencies
- Custom GPT builders

## Core Principle

Build useful things that sell without feeling like sales.

A strong engineering-as-marketing asset should:

- Solve one narrow problem
- Provide immediate value
- Produce a useful output
- Explain the next step
- Capture or route qualified interest where appropriate
- Work without unnecessary friction
- Avoid unsupported claims
- Be reusable across pages, GPTs, and campaigns

## Asset Types

### Calculator

Best for numerical planning, forecasting, or comparison.

Examples:

- Ad spend cash-flow calculator
- Safe ad spend estimator
- Funding payment estimator
- Inventory runway calculator
- Cash-gap calculator
- Partner commission estimator

Required fields:

- Inputs
- Formula assumptions
- Output metrics
- Disclaimer
- CTA
- Reset and copy/download behavior

### Scorecard

Best for readiness, fit, maturity, or risk evaluation.

Examples:

- Funding readiness scorecard
- Business credit setup scorecard
- CRM hygiene scorecard
- AI workflow readiness scorecard
- Partner enablement scorecard

Required fields:

- Question set
- Scoring logic
- Score bands
- Recommendations
- Disclaimer
- CTA

### Directory

Best for browsing structured resources.

Examples:

- Agent directory
- Skill catalog
- Partner provider directory
- Tool directory
- Prompt pack directory
- Template library

Required fields:

- Search
- Filters
- Categories
- Cards or table
- Data source
- CTA
- Empty state

### Generator

Best for creating reusable text, markdown, JSON, prompts, pages, or specs.

Examples:

- Prompt generator
- Skill builder
- Partner resource-card generator
- Schema starter generator
- Landing page copy generator
- Profile page generator

Required fields:

- Input form
- Output preview
- Copy button
- Download button
- Required field validation
- Public-safe guardrails

### Checklist

Best for procedural readiness.

Examples:

- Funding document checklist
- Partner launch checklist
- Vercel deployment checklist
- Custom GPT publishing checklist
- AI workflow audit checklist

Required fields:

- Task list
- Category grouping
- Completion tracking
- Export or copy option
- Next step

## Tool Spec Format

```md
# [Tool Name]

## Purpose

What problem the tool solves.

## User

Who uses the tool.

## Inputs

- Input 1
- Input 2

## Outputs

- Output 1
- Output 2

## Logic

Explain formulas, scoring, or generation logic.

## UX Requirements

- Requirement 1
- Requirement 2

## CTA

Primary:
Secondary:

## Safety / Disclaimer

What the tool must not claim.

## Suggested Files

- index.html
- styles.css
- script.js
- README.md
```

## CTA Strategy

Use CTAs that match the tool’s job.

Strong CTAs:

- Run the calculator
- Check readiness
- Generate prompt pack
- Build resource card
- Compare options
- Download template
- Browse related agents
- Start partner application
- View next steps

Weak CTAs:

- Learn more
- Submit
- Click here
- Get started with no context
- Apply now before education

## Public-Safe Rules

For funding, finance, business credit, legal, tax, or platform content:

- Do not promise approvals.
- Do not promise funding.
- Do not promise credit outcomes.
- Do not promise revenue.
- Do not promise ranking or traffic.
- Do not imply professional advice.
- Use educational and readiness language.
- Show assumptions.
- Explain limitations.
- Include human review where needed.

## Standard Engineering-as-Marketing Agent Output

```md
## Tool Summary

- Tool name:
- Audience:
- Problem solved:
- Asset type:
- Primary CTA:
- Secondary CTA:
- Risk level:

## Required Inputs

- Input 1
- Input 2

## Outputs

- Output 1
- Output 2

## Logic

Explain formulas, scoring, or generation rules.

## Recommended Files

- index.html
- styles.css
- script.js
- README.md

## Page Sections

- Hero
- How it works
- Tool interface
- Results
- Examples
- CTA
- Disclaimer
- FAQ

## Guardrails

- Guardrail 1
- Guardrail 2
```

## Related Repo Paths

```text
knowledge-base/engineering-as-marketing/
portfolio/vercel/
examples/content-ops/
examples/automation/
schemas/
prompt-generator.html
skill-builder.html
```

## Maintenance Checklist

- [ ] Tool specs solve a narrow problem.
- [ ] Inputs and outputs are clear.
- [ ] CTA matches user intent.
- [ ] Assumptions are documented.
- [ ] Public-safe rules are included.
- [ ] Examples are synthetic.
- [ ] Suggested files are repo-ready.