Team Bio Lookup — HAQQ Leadership and Advisor Profiles
When to use this
Invoke when:
- A partner page or website needs team bio cards
- An investor asks "who is behind HAQQ?"
- An event organizer needs a speaker bio for a HAQQ team member
- A press inquiry requires a founder or leadership quote attribution
- An in-product "About" screen needs team profiles
Bio structure — standard format
Each team bio should contain:
| Field |
Description |
| Name |
Full name |
| Title |
Current role at HAQQ |
| Photo |
Reference to photo asset (if available) |
| Short bio (50–75 words) |
Role summary, relevant background, why they are at HAQQ |
| Long bio (150–200 words) |
Career arc, key achievements, HAQQ focus area, personal anchor |
| LinkedIn |
Profile URL |
| Audience variant |
Investor / Press / Partner / Conference |
Bio categories
Founders and C-Suite
The core leadership team building HAQQ. Bios in this category should emphasize:
- Domain expertise (legal, technology, MENA market)
- Founding story and mission motivation
- Specific jurisdictional or technical depth
- Prior company-building or legal-practice experience
Advisors
HAQQ's advisor network includes legal practitioners, technologists, and regional market experts. Advisor bios should:
- Highlight the specific area of advisory contribution (e.g., "MENA regulatory strategy", "AI infrastructure", "bar association relations")
- Note the advisor's primary affiliation (law firm, university, company)
- Be shorter than founder bios: 50–100 words for most contexts
Key Hires
Senior hires in product, engineering, legal, and operations. Bios should:
- Focus on what the individual brings to HAQQ's specific growth phase
- Mention notable prior experience briefly
- Keep length proportionate to seniority
Tone guidelines by audience
| Audience |
Tone |
Emphasis |
| Investor / VC |
Confident, track-record-focused |
Prior experience, domain depth, execution credibility |
| Press / Journalist |
Accessible, quotable |
Founding story, mission, MENA context |
| Partner / BD |
Professional, collaborative |
Relevant expertise, relationship-building background |
| Conference / Event |
Engaging, punchy |
Key credential + hook for the audience |
| In-product / Users |
Warm, human |
Why this person cares about legal access |
What to exclude from all bios
- Do not include personal information beyond what the individual has publicly shared (no home city, no personal family details)
- Do not fabricate credentials, positions, or dates
- Do not describe advisors as "employees" or "team members" if they are advisors
- Do not include any financial information (compensation, equity) in any public-facing bio
Keeping bios current
Bios should be reviewed and updated:
- When a team member's title or role changes
- When a significant new achievement or milestone is announced (funding round, award, publication)
- At least annually for active team members and key advisors
Related skills
- [[academy-company-bio]]
- [[academy-partnership-pitch]]
- [[academy-vc-program-pitch]]
1---2name: academy-team-bio-lookup3description: Team Bio Lookup — HAQQ Leadership and Advisor Profiles4---56# Team Bio Lookup — HAQQ Leadership and Advisor Profiles78## When to use this910Invoke when:11- A partner page or website needs team bio cards12- An investor asks "who is behind HAQQ?"13- An event organizer needs a speaker bio for a HAQQ team member14- A press inquiry requires a founder or leadership quote attribution15- An in-product "About" screen needs team profiles1617## Bio structure — standard format1819Each team bio should contain:2021| Field | Description |22|---|---|23| Name | Full name |24| Title | Current role at HAQQ |25| Photo | Reference to photo asset (if available) |26| Short bio (50–75 words) | Role summary, relevant background, why they are at HAQQ |27| Long bio (150–200 words) | Career arc, key achievements, HAQQ focus area, personal anchor |28| LinkedIn | Profile URL |29| Audience variant | Investor / Press / Partner / Conference |3031## Bio categories3233### Founders and C-Suite34The core leadership team building HAQQ. Bios in this category should emphasize:35- Domain expertise (legal, technology, MENA market)36- Founding story and mission motivation37- Specific jurisdictional or technical depth38- Prior company-building or legal-practice experience3940### Advisors41HAQQ's advisor network includes legal practitioners, technologists, and regional market experts. Advisor bios should:42- Highlight the specific area of advisory contribution (e.g., "MENA regulatory strategy", "AI infrastructure", "bar association relations")43- Note the advisor's primary affiliation (law firm, university, company)44- Be shorter than founder bios: 50–100 words for most contexts4546### Key Hires47Senior hires in product, engineering, legal, and operations. Bios should:48- Focus on what the individual brings to HAQQ's specific growth phase49- Mention notable prior experience briefly50- Keep length proportionate to seniority5152## Tone guidelines by audience5354| Audience | Tone | Emphasis |55|---|---|---|56| Investor / VC | Confident, track-record-focused | Prior experience, domain depth, execution credibility |57| Press / Journalist | Accessible, quotable | Founding story, mission, MENA context |58| Partner / BD | Professional, collaborative | Relevant expertise, relationship-building background |59| Conference / Event | Engaging, punchy | Key credential + hook for the audience |60| In-product / Users | Warm, human | Why this person cares about legal access |6162## What to exclude from all bios6364- Do not include personal information beyond what the individual has publicly shared (no home city, no personal family details)65- Do not fabricate credentials, positions, or dates66- Do not describe advisors as "employees" or "team members" if they are advisors67- Do not include any financial information (compensation, equity) in any public-facing bio6869## Keeping bios current7071Bios should be reviewed and updated:72- When a team member's title or role changes73- When a significant new achievement or milestone is announced (funding round, award, publication)74- At least annually for active team members and key advisors7576## Related skills7778- [[academy-company-bio]]79- [[academy-partnership-pitch]]80- [[academy-vc-program-pitch]]