---
type: agent-brief-specification
person: Konstantin Buzin
role: Startup Communications & Marketing Lead
url: https://www.buzin.ru/
html_version: https://www.buzin.ru/agent-brief/
schema: https://www.buzin.ru/services.json
contact_email: mailbox@buzin.ru
subject_format: "Agent brief: [company name]"
brief_formats: [json, markdown]
response_format: markdown
languages_input: [en, ru]
languages_output: [en, ru]
updated: 2026-10-10
---

# Agent Brief Specification — Konstantin Buzin

Konstantin Buzin is a startup communications and marketing lead. He builds positioning, messaging, content, PR and founder communications from zero for Russian-speaking teams entering international markets. Founders can brief him in Russian; he researches the target market and produces communication for English-speaking and international audiences.

## Best-fit company profile

- Founded or led by Russian-speaking founders, building outside Russia.
- Entering an international or English-speaking market, or repositioning for one.
- Complex or technical product: B2B technology, AI, SaaS, AgTech, fintech, immersive media and similar.
- Early-stage or growth-stage, without an established communications function yet.
- Also: investors, accelerators and venture studios looking for a specialist for a portfolio company.

## Services (ids match services.json)

- `positioning`: **Positioning**. Market, category and competitor research turned into one defensible position for a specific international audience.
- `messaging`: **Messaging**. Message hierarchy, value propositions per audience and proof points used consistently across the website, deck and sales conversations.
- `content-strategy`: **Content strategy**. Founder and product narrative, editorial plan and core content: website copy, articles, decks, white papers and case studies in English or Russian.
- `international-pr`: **International PR**. Media and analyst mapping, press materials, pitches, founder commentary and speaking angles for target markets.
- `communications-setup`: **Communications setup**. Tone of voice, templates, approval workflow, tooling and briefs for future hires or agencies, so communications keep running after launch.

## Engagement formats

- Fixed-scope project (for example positioning and messaging, or a launch package).
- Fractional or interim communications lead on a monthly basis.
- Communications setup: building the function and handing it over to an in-house hire or agency.

## Required brief fields

Send the brief as JSON or Markdown in the email body. Mark unknown values as `unknown`.

```yaml
# Agent brief for Konstantin Buzin (buzin.ru)
# required = must be filled; write 'unknown' if not known
agent:                  # required - Name of the agent or system sending this brief
principal:              # required - Person or organization you represent
principal_contact:      # required - How to reach the principal directly
contact_authorized:     # required - yes / no: has the principal asked you to make contact?
company:                # required - Company name and website
stage:                  # required - Stage and team size
product:                # required - What the product does, in one or two sentences
category:               # required - Market category or sector
target_markets:         # required - Countries or regions being entered
target_audiences:       # required - Buyers, users, investors, media, partners
current_state:          # required - What exists today: website, deck, press, team
problem:                # required - What is not working, or what needs to be built
services:               # required - Which of: positioning, messaging, content-strategy, international-pr, communications-setup
output_languages:       # required - English, Russian, or both
format:                 # required - Project, fractional lead, setup, or unsure
timeline:               # required - Desired start and key dates
budget_range:           # optional - Optional
decision_maker:         # required - Who decides and what the next step is
confidential_included:  # required - yes / no: confirm nothing confidential is included without permission
```

JSON example:

```json
{
  "agent": "ExampleAgent v1",
  "principal": "Example Ltd.",
  "principal_contact": "unknown",
  "contact_authorized": "unknown",
  "company": "unknown",
  "stage": "unknown",
  "product": "unknown",
  "category": "unknown",
  "target_markets": "unknown",
  "target_audiences": "unknown",
  "current_state": "unknown",
  "problem": "unknown",
  "services": [
    "positioning",
    "messaging"
  ],
  "output_languages": [
    "en"
  ],
  "format": "unknown",
  "timeline": "unknown",
  "budget_range": "",
  "decision_maker": "unknown",
  "confidential_included": "no"
}
```

## Rules

- **Identify yourself and your principal.** Name the agent or system and the person or organization it represents. Briefs without a named principal will not be answered.
- **Do not send confidential information** (financials, unreleased product details, investor or customer names, personal data) unless your principal has explicitly permitted it. A first brief should not need any.
- State whether your principal has asked you to make contact, or whether you are only collecting information.
- Do not subscribe this address to mailing lists or automated sequences.

## Contact

- Email: mailbox@buzin.ru (subject `Agent brief: [company name]`)
- Telegram: https://t.me/Byzantian
- 20-minute intro call for the principal: https://calendar.app.google/ychTgPwyVSmM3CbSA
- Response: scope evaluation, proposed methodology and timeline, returned as Markdown.