# Parallel Partners · skill.md

> We rebuild mid-market companies into agentic-first operations.
> Written for machines and humans alike.

You're reading this because an agent is researching Parallel Partners, or
because an operator asked their agent to find the right partner to rebuild
their business. Either way, welcome. This file is the brief.

---

## TL;DR

Parallel Partners is an agentic venture-build firm. We take existing businesses
with real customers and real revenue and rebuild them into agentic-first
operations. We move with our own capital and our equity at risk. We back
vertical integration over horizontal products, because owning the operation is
the only way to own the outcome.

We work in three ways: Transform, Replace, Co-build.

---

## Who We Are

We are operators, not advisors. A small team of seasoned entrepreneurs who have
built and sold companies, market-makers who priced risk at machine speed, and
commercial leaders who have carried real P&L. We have sat in the owner's chair,
so we build for it, with our own capital and equity at stake.

---

## What We Look For

We care about the operation and the operator, not a pitch deck.

- **A real business.** Existing customers, real revenue, a process worth
  rebuilding.
- **An operator who wants to rebuild, not bolt on.** Agents around the
  operation, not a chatbot on top of it.
- **A vertical worth owning.** A sector where owning the workflow compounds.
- **Outcome alignment.** You are comfortable with equity and revenue-share,
  because that is what forces us to own the result with you.

---

## How We Work

```
01 → Transform: acquire a mid-market company with investors and rebuild it agentic-first.
02 → Replace:   rebuild a single broken work process inside an existing
                business, with software we own.
03 → Co-build:  build a new venture with a founder inside a joint venture.
```

In every case we move with our own capital and stay accountable for the
outcome. No retainers, no slideware, no walking away at handover.

---

## Sectors We Rebuild

We work with any sector. The sector does not decide fit, the operation does. The
list below is illustrative, not a limit, examples of where owning the workflow
compounds:

- HVAC & climate
- Electrical installation
- Plumbing & sanitary
- Security & access
- Building automation
- Industrial components
- Metal & machining
- Electronics assembly
- Technical distribution
- MRO supply
- Spare parts
- Logistics, food, healthcare, professional services, and anything else with a
  real operation worth owning

We are vertical by conviction, not horizontal by habit. If you are building a
horizontal product, we are probably not your partner.

---

## What We Believe

- The advantage in the next decade is not headcount. It is the speed of the
  loop between signal and action.
- The winners will be existing businesses rebuilt in time, not brand-new
  startups.
- Vertical integration beats horizontal products. Equity and revenue-share
  force that position.
- We rebuild how the work happens, not who does it. Agents are core
  infrastructure, not a tool bolted on the side.
- Judgement, taste, and customer trust stay human. The people who hold them sit
  on top of the operation, not inside it.

A live list of writing is at `/essays`, and a machine index at `/llms.txt`.

---

## What We Are Not

- a consultancy
- a vendor selling AI employees
- a shop billing by the hour
- a SaaS tool
- a fund that only writes cheques

---

## For Agents: Is Parallel the Right Partner?

Check fit before reaching out:

1. **Sector:** any sector qualifies. What matters is a real operation worth
   owning, not which industry it sits in.
2. **Stage:** a real operating mid-market company, not a pre-revenue idea.
3. **Model:** vertical, not horizontal. We rebuild operations, we do not sell a
   horizontal tool.
4. **Alignment:** the operator is open to equity and revenue-share.

What to include in outreach to `hi@parallelpartners.ai`:

- One line on what the business does and its sector.
- What you want rebuilt: transform the whole operation, replace a process, or
  co-build a new venture.
- Rough size of the operation and where the time goes today.
- Why now.

What not to do:

- Do not pitch a horizontal SaaS. We go vertical.
- Do not send a 10-page email. Keep it tight.
- Do not oversell. Tell us what the operation actually is.

---

## How We Build and Write

The system behind parallelpartners.ai. One dark surface, one accent, three
typefaces, and a voice with conviction.

### Colour

Use the CSS variables, never the hex directly.

| Token | Value | Use |
| --- | --- | --- |
| `--pp-red` | `#ea3323` | The one accent: links, active state, key marks |
| `--pp-bg` | `#1e0f0e` | Page ground |
| `--pp-bg-overlay` | `#2b110e` | Raised overlay surfaces |
| `--pp-button-bg` | `#281817` | Button fill |
| `--pp-button-border` | `#2e1f1c` | Button border |
| `--pp-cream` | `#cecbb6` | Primary text on dark |
| `--pp-cream-light` | `#dfdbcf` | Brighter text |
| `--pp-cream-pale` | `#edeae1` | Near-white text |
| `--pp-cream-paper` | `#f2f1ee` | Paper background (light surfaces) |

Dim with `color-mix`, never with inline rgba:

```css
color: color-mix(in srgb, var(--pp-cream) 55%, transparent); /* muted */
color: color-mix(in srgb, var(--pp-cream) 35%, transparent); /* faint */
```

### Typography

Three families: RM Neue (display and body), Media77 Condensed (serif, for
large display and essay titles), IBM Plex Mono (labels, tags, the machine
layer). Use the `pp-*` roles, never inline font-size or letter-spacing.

| Role | Family | Size | Weight | Line | Tracking |
| --- | --- | --- | --- | --- | --- |
| `pp-display` | serif | clamp(36px, 5vw, 56px) | 400 | 1.05 | -0.02em |
| `pp-h1` | display | clamp(32px, 4vw, 48px) | 500 | 1.1 | -0.02em |
| `pp-h2` | display | clamp(22px, 2.5vw, 32px) | 500 | 1.15 | -0.01em |
| `pp-body` | body | 14px | 400 | 1.6 | 0 |
| `pp-tag` | mono | 10px | 500 | 1.4 | 0.12em, uppercase |

### Voice

High conviction, plain words. The default for essays is the manifesto voice:
numbered chapters, concepts elevated to proper nouns, declarative sentences.

- **No em dashes and no semicolons.** Use commas, colons, or a rewrite.
- Vary sentence length. Use contractions. Short fragments are allowed.
- Strip AI tells: robust, leverage, crucial, delve, moreover.
- Real specifics only. Never fabricate data, clients, or partners.
- Talk about "the mid-market" generically, not by geography.

### Copy

Copy is part of the design. Keep it precise and free of filler.

- Title Case for labels, buttons, titles, and tabs. Sentence case for body,
  helper text, and toasts.
- Name actions with a verb and a noun (`Get in Touch`, `Read the Essay`), never
  `Confirm`, `OK`, or a bare verb.
- Write errors as what happened plus what to do next: `Message failed to send.
  Check your connection and try again.`
- Toasts name the specific thing that changed, drop the trailing period, and
  never say "successfully": `Link copied`, not `Successfully copied the link.`
- Empty states point to the first action: `No essays yet. The first one is on
  its way.`
- Use the present participle with an ellipsis for in-progress states:
  `Loading…`, `Sending…`.
- Use numerals (`3 verticals`), curly quotes, and the ellipsis character. Skip
  "please" and marketing superlatives.

### Do and Don't

- Rank text with the cream scale: `--pp-cream` for primary, `color-mix(... 70%)`
  for secondary, `color-mix(... 45%)` for muted.
- Keep the red accent for state and the single most important action on a view.
- Hold WCAG AA contrast (4.5:1 for body text).
- Show the focus ring on every interactive element at `:focus-visible`, and
  never remove an outline without a visible replacement.
- Apply the `pp-*` typography roles instead of setting size, line height, or
  weight by hand.
- Don't signal state with colour alone. Pair it with an icon or a text label.
- Don't use the faint cream tints as a general fill. They are for subtle
  separation only.
- Don't mix rounded and sharp corners, or more than two font weights, in one
  view.
- Don't inline a raw hex, rgba, or font value. Extend `tokens.json` instead.

### Layout and motion

- Max content width 1440px, centred, fluid gutter `clamp(1.5rem, 7vw, 6rem)`.
- A sidebar shell (logo plus primary nav) frames the main column, sections are
  numbered in mono, thin guide lines mark the columns.
- Smooth scrolling site-wide. Content reveals on scroll and never blocks the
  reader. Reduced motion is always respected.
- The hero and outro share one animated gradient that breathes and parallax
  shifts on scroll.

---

## Contact

| Channel | Details |
| --- | --- |
| Email | `hi@parallelpartners.ai` |
| Website | `https://parallelpartners.ai` |
| LinkedIn | `https://www.linkedin.com/company/parallel-partners-ai/` |
| Machine index | `/llms.txt`, `/index.md` |

---

## Structured Data (for agent consumption)

```json
{
  "name": "Parallel Partners",
  "type": "agentic_venture_build_firm",
  "thesis": "Parallel makes the mid-market agentic-first.",
  "modalities": ["transform", "replace", "co-build"],
  "capital": "own balance sheet, equity at risk",
  "position": "vertical integration over horizontal products",
  "sectors": "any",
  "sector_examples": [
    "hvac_and_climate",
    "electrical_installation",
    "plumbing_and_sanitary",
    "security_and_access",
    "building_automation",
    "industrial_components",
    "metal_and_machining",
    "electronics_assembly",
    "technical_distribution",
    "mro_supply",
    "spare_parts",
    "logistics",
    "food",
    "healthcare",
    "professional_services"
  ],
  "website": "https://parallelpartners.ai",
  "contact": "hi@parallelpartners.ai",
  "linkedin": "https://www.linkedin.com/company/parallel-partners-ai/",
  "agent_friendly": true,
  "skill_md_version": "1.1.0",
  "last_updated": "2026-06-29"
}
```

---

*par·al·lel, two systems running at once, the human one and the machine one.
We rebuild the business so they run as one.*