AGENTS.md

AGENTS.md

Project goal

This is Mahadev Upadhyayula’s personal website. The current goal is to position it as a practical B2B SaaS AI workflow-product site.

Primary positioning: Mahadev builds human-approved AI workflow products for B2B SaaS product, engineering, and implementation teams. The work turns scattered inputs and signals into structured, validated, reviewable outputs.

Copy principles

  • Write for buyers, not recruiters first.
  • Be specific and concrete.
  • Prefer “quality signals,” “implementation inputs,” “product evidence,” “reviewable workflows,” and “human approval” over generic AI language.
  • Avoid hype words like “AI magic,” “revolutionary,” “cutting-edge,” or “agentic transformation.”
  • Keep paragraphs short and scannable.

Design principles

  • Premium B2B SaaS feel.
  • Dark navy / near-black backgrounds.
  • White text.
  • Electric blue accents.
  • Rounded cards.
  • Clear CTA buttons.
  • No generic robot imagery.
  • Keep mobile readability strong.

Core CTA

Primary CTA: Discuss a Workflow Prototype

Secondary CTA: Explore Workflow Examples

Lead CTA: Send Workflow Inquiry

Core workflow diagram

Use this pattern where relevant: Scattered Inputs → AI Processing → Validation → Human Approval → Reviewable Output

Commercial priorities

Prioritize these services and case studies:

  1. AI Workflow Prototype Sprint
  2. Implementation Intelligence Workspace
  3. Quality Intelligence Workbench
  4. Product Evidence Workbench
  5. Existing CRM hygiene, pre-CRM research, quote/proposal, content, and custom workflow capabilities as secondary offers

Engineering rules

  • Do not add dependencies unless explicitly required.
  • Preserve existing routes unless asked to rename them.
  • Reuse existing layout/components/styles where possible.
  • Keep changes small and reviewable.
  • Run the project’s build command before final response.
  • Report changed files and verification results.

Done means

A task is complete only when:

  • The requested content/UI change is implemented.
  • Existing important routes still work.
  • Build passes or any failure is clearly explained.
  • The final response includes changed files and verification steps.