Software House Organizational Structure Org Chart Infographic

Tech architecture infographic titled "Software House Organizational Structure" using archetype SYSTEM ARCHITECTURE adapted as an organizational structure grid. Create a flat departmental grid org chart for a small software house team of 11–20 people, with text-only nodes and no avatars, no photos, no personal names. Hand-drawn whiteboard aesthetic, minimal monochrome palette, tasteful framing, clean spacing, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout.

Render grouped labeled BOXES connected by ARROWS showing reporting direction and collaboration flow. Each box must contain a small generic icon, a role or department name in sharp readable English, and a one-line role description in English. Visually group nodes into departments with subtle whiteboard outlines.

Top level box:
- Managing Director — "Sets strategy, budget, and delivery priorities"

Second level department lead boxes reporting to Managing Director:
- Delivery / Operations Manager — "Coordinates projects, staffing, and timelines"
- Technical Lead — "Owns architecture, engineering standards, and code quality"
- Product / Project Manager — "Defines scope, backlog, and client requirements"
- Sales & Account Manager — "Handles client acquisition and account growth"
- Finance & HR / Administration — "Manages hiring, payroll, contracts, and policies"

Engineering department grouped under Technical Lead with small-team nodes:
- Frontend Developer — "Builds browser UI and client-side features"
- Backend Developer — "Implements APIs, business logic, and integrations"
- Full-Stack Developer — "Works across UI, API, and database layers"
- QA Engineer — "Tests releases and verifies software quality"
- UI/UX Designer — "Designs interfaces, prototypes, and user flows"
- DevOps / Cloud Engineer — "Maintains deployment, CI/CD, and infrastructure"

Delivery and product group connections:
- Business Analyst — "Translates client needs into clear requirements"
- Scrum Master / Team Coordinator — "Facilitates workflow, standups, and delivery rituals"

Commercial and support group under Sales & Account Manager and Finance & HR / Administration:
- Marketing Specialist — "Supports lead generation and brand visibility"
- Recruiter / People Operations — "Sources candidates and supports onboarding"

Use hierarchical reporting lines from top to department leads to team roles. Also add lighter dotted collaboration arrows between Product / Project Manager, Technical Lead, QA Engineer, UI/UX Designer, and Delivery / Operations Manager.

Arrow labels must be short English phrases such as:
- "strategy & budget"
- "delivery goals"
- "technical guidance"
- "project requirements"
- "client feedback"
- "quality reports"
- "release coordination"
- "hiring requests"
- "sales pipeline"

Add a numbered legend 1–7 in English explaining the lifecycle of work in this organization:
1. Client opportunity enters through Sales & Account Manager.
2. Product / Project Manager and Business Analyst refine scope and requirements.
3. Managing Director approves priorities, budget, and staffing.
4. Technical Lead and UI/UX Designer shape solution approach and experience.
5. Developers and DevOps build, integrate, and deploy the product.
6. QA Engineer validates quality and Delivery / Operations Manager coordinates release readiness.
7. Account, finance, and people operations support retention, billing, and team growth.

Visual style: hand-drawn marker lines, whiteboard sketch feel, flat departmental grid, monochrome black/charcoal/soft gray palette, minimal shading, crisp typography, subtle department containers, balanced composition, professional but approachable mood. No decorative clutter. Emphasize grouped departments, hierarchy, and reporting clarity.

All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-person names or photos. Generic role titles. Tasteful framing throughout.