Consultant profile

Consultant Profile

Create consultant profiles that sell a clear professional thesis instead of merely listing a career in reverse chronological order.

The profile's job is to help a buyer, recruiter, partner, or staffing lead quickly understand:

• what this consultant is unusually good at
• which kinds of organizations trust them
• which industries and operating contexts they know
• what level of complexity, responsibility, and impact they have handled
• what they should be hired for next

First Read

Read these references before making substantive changes:

• Profile principles - research synthesis, project-prominence model, regional/channel strategy, writing formulas, and audit checklist
• Language and persuasion - tone calibration, positive-but-earned framing, plain-language editing, human voice, and ethical marketing psychology
• Narrative arc - professional storyline, recurring themes, project connections, and "no loose pile of projects" structure
• Interview and completion - source inventory, gap analysis, interview questions, project completeness, and reference/testimonial mining
• Personality and boundaries - professional personality, opinionated positioning, limits, working style, design background, and self-learner signals

Core Workflow

1. Identify the target reader and buying situation.

   • Distinguish between project staffing, direct client acquisition, recruiter screening, partnership, and public website profile.
   • Identify the channel: PDF/CV, website, LinkedIn, XING, marketplace profile, proposal bio, or internal supplier profile.
   • Identify the country/market and language: Germany, Austria, Switzerland, EU/international English, US/global English, or bilingual.
   • Combine country with buying channel before applying format conventions. Germany, Austria, and Switzerland share some credibility-first expectations, but they are not one fixed CV format; direct-buyer profiles, staffing CVs, and marketplace cards also solve different jobs.
   • When a named intermediary or marketplace is in scope, read Consultant marketplace profile fields. Treat its provider matrix as a dated adapter, not a universal or permanent schema.
   • Read accepted ADRs and brand or editorial guidance for audience relationship, form of address, voice, tone, terminology, and channel exceptions. Use decision-records when this work establishes or changes a durable cross-channel communication direction.
   • If the target is unclear, infer the most likely one from the prompt and state the assumption briefly.

2. Extract the consultant's positioning thesis.

   • Reduce the profile to one sharp sentence: "[Role/specialty] who helps [type of organization] achieve [business/technical outcome] in [contexts]."
   • Base this on evidence from projects, clients, industries, scope, and recurring strengths.

3. Build an evidence map before rewriting.

   • List projects, clients, roles, industries, scale, technologies, seniority, outcomes, and notable constraints.
   • Mark each item with evidence types: brand signal, business impact, technical depth, leadership/stakeholder complexity, industry relevance, recency, and uniqueness.
   • Treat recommendations and testimonials as attributed external evidence. Preserve author, relationship, role/company at the time, date, original language/text, source locator, known reuse restrictions or sensitivities, selected excerpts, translations, and the claims they support.
   • When an opportunity brief or project request exists, separate explicit requirements, useful signals, and contextual preferences. Map each one to supplied evidence, and leave unsupported or unknown criteria unresolved instead of inferring a match or inventing a percentage score.

4. Run completeness and interview mode when data is missing or uncertain.

   • Inventory sources such as the current website, old website, LinkedIn profile, LinkedIn recommendations, CVs, project notes, proposals, and testimonials.
   • Separate known facts, plausible inferences, and unknowns.
   • Ask small, prioritized batches of questions instead of trying to solve all gaps at once.
   • Extract project facts and recommendation signals before rewriting. Use the user's LinkedIn data export or supplied copies rather than scraping profiles.

5. Find the professional arc.

   • Identify recurring themes across projects: industries returned to, capabilities that deepen, scale that increases, and lessons reused from one context in another.
   • Connect projects where later work clearly builds on earlier experience.
   • Use the arc to explain why the consultant's profile is more than a loose collection of engagements.
   • Keep it concise: create context and momentum, not a biography or a sports-documentary script.

6. Choose project prominence by relevance, not chronology alone.

   • Feature 3-5 "signature projects" or "selected highlights" near the top.
   • Promote older but high-signal work when it proves the desired positioning.
   • Keep a secondary "additional selected projects" list for breadth, not for important work that merely happens to be older.
   • Treat recognizable client names as signal only when the supplied evidence, target audience, and publication permissions support using them.

7. Rewrite projects as proof points.

   • Prefer Outcome -> Action -> Scope when impact is known.
   • Prefer Challenge -> Role -> Deliverable when outcomes are confidential or unavailable.
   • Name the industry, organization type, scale, and responsibility level where possible.
   • Avoid vague responsibility lists and generic technology stacks without business context.

8. Make the profile scannable.

   • Put the strongest positioning and proof in the first screen/page.
   • Use front-loaded headings, short bullets, and grouped evidence.
   • Avoid walls of text and burying high-signal clients in long chronological lists.
   • Let every section earn its place by helping the target reader perceive relevant fit; design should reinforce hierarchy rather than decorate the document.

9. Calibrate personality, values, and boundaries.

   • Identify what makes the consultant memorable: working style, professional values, taste, judgment, collaboration style, and recurring stances.
   • Treat personality as a buyer-fit layer, not a decorative sidebar. The reader should understand what kind of person they may hire, what gives them energy, how they think, and what they want to create or improve.
   • Translate raw personality markers into buyer-safe language. For example, "Nein-Sager" may become "constructive dissent", "clear product judgment", "says no when it protects focus, quality, or users", or "brings clear boundaries to ambiguous product work".
   • State relevant boundaries when they clarify fit: what the consultant does well, what they do not pretend to do, which roles they avoid, and where they need complementary specialists.
   • Use background signals when they explain strengths. A design/webdesign origin, visual judgment, layout/color sensitivity, designer collaboration, and autodidactic engineering path can support a bridge positioning between product, design, and software delivery.
   • Include personal motivation and professional ambition when they make the profile more human and commercially relevant. Avoid private biography that does not help the reader decide fit.
   • Keep personality grounded in proof. Do not make the profile quirky for its own sake; show how the stance improves outcomes, collaboration, quality, or focus.

10. Localize the profile instead of translating it literally.

• For German-language profiles, favor precise, credible, evidence-heavy language and avoid exaggerated sales claims, then apply country-specific conventions only where the target channel needs them.
• Do not transfer employment-application conventions automatically to consultant sales profiles. Treat photo, personal data, references, and page count as country- and channel-dependent rather than universal DACH requirements.
• For staffing, supplier, and marketplace channels, keep a stable master field model and map it to the provider's current labels. Separate reusable profile facts, private account/application data, buyer-facing operational fit, and platform-owned signals.
• Surface supplied operational fit such as availability, capacity, location/time zone, remote/on-site setup, travel readiness, languages, and engagement model. Include a rate only when the channel expects it and the user supplied it; preserve amount, currency, unit, and applicability.
• Use CEFR levels for languages when useful. Describe tool proficiency with evidence such as project context, recency, depth, or years used instead of vague self-ratings.
• For US/global English profiles, make the value proposition more explicit and outcome-led.
• For US-facing resumes, omit photos and sensitive personal details.
• For LinkedIn, combine searchable keywords with a human first-person summary, visible proof, recommendations, media, and posts.
• Keep the original wording of external quotes as the factual source. A localized quotation must be visibly labelled as a translation, remain faithful in meaning, preserve local attribution, and link or point to the original where practical. Mark omissions and never splice fragments into a stronger claim.
• Keep bilingual variants aligned in facts but adapted in tone, section order, and terminology.

11. Run a language and persuasion pass.

• Make claims clear, concise, active, and specific.
• Add positive framing where the evidence supports it; do not leave strong work sounding neutral or accidental.
• Assume readers discount cautious self-presentation: state credible strengths warmly and explicitly while keeping every claim anchored.
• Remove empty hype, generic AI-ish phrasing, and unsupported superlatives.

12. Preserve truthfulness.

• Do not invent metrics, client claims, leadership scope, or outcomes.
• If metrics are missing, use bounded qualitative evidence: "enterprise-scale", "regulated banking environment", "multi-brand retail group", "telecommunications customer platform", or similar factual context.
• Flag claims that need confirmation before publishing.

Recommended Output

For an audit, return:

1. Profile Thesis - one proposed positioning sentence.
2. Prominence Map - which projects should be signature, supporting, or archive-level, with rationale.
3. Source and Gap Inventory - what is known, missing, inferred, duplicated, or needs permission.
4. Interview Questions - prioritized questions that resolve the most important uncertainties.
5. Narrative Arc - the through-line that connects projects, capabilities, industries, and recurring strengths.
6. Personality, Boundaries, and Buyer Fit Strategy - which values, motivations, stances, strengths, limits, and background signals should be visible, and how to word them professionally.
7. External Proof Strategy - which recommendations should become direct quotes, claim support, working-style evidence, or source-only material; include attribution, reuse sensitivity, translation, and source-link handling.
8. Channel and Market Strategy - how the profile should differ for direct buyers, staffing/supplier channels, marketplaces, PDF/CV, website, LinkedIn/XING, and Germany, Austria, Switzerland, EU/international, or US audiences.
9. Provider Field Mapping - when a named intermediary or marketplace is in scope, map its current documented fields to the stable master model and label each as reusable, private/account, operational/application, or platform-owned.
10. Structure - proposed profile sections in order.
11. Voice Strategy - recommended German-language credibility-first tone, country/channel adaptations, English/international tone, LinkedIn tone, and any "more positive" variant.
12. Rewrite Samples - improved headline, intro, LinkedIn/About version if relevant, and 3-5 project entries.
13. Gaps - missing metrics, facts, known quote restrictions, client permissions, provider-field volatility, or platform/API constraints to verify.

For a full rewrite, return a complete profile with:

• headline
• 3-5 line executive summary
• short professional arc / through-line
• optional personal motivation, working-principles, or role-fit block
• capability pillars
• selected highlights or signature projects
• industry/client context
• optional selected-recommendations or "voices from collaboration" block with local attribution and visibly labelled translations
• optional operational-fit block for staffing, supplier, or marketplace channels
• optional provider field map when a named intermediary or marketplace is in scope
• additional selected projects
• LinkedIn/About and headline variants when a social profile is in scope
• tone variants when useful: restrained or warmer German-language copy, country/channel adaptations, international English, LinkedIn
• skills/tooling only where it reinforces the thesis

Quality Bar

Prefer concrete, commercially legible language over career-history narration. A strong output should make the reader think, within 30 seconds: "I understand what this person does, where they have done it, and why they are credible for this kind of work."

Routing Boundaries

• Route the acquisition overlay — target-buyer path, network, conversation, content, and pipeline strategy for a completed profile — to linkedin-social-selling. Keep professional evidence and field-level profile content in this skill.