---
name: sales-manypixels
description: "ManyPixels (manypixels.co) platform help — a flat-monthly UNLIMITED-request graphic-design subscription (design-as-a-service): submit unlimited requests, human designers deliver them through a SERIALIZED async queue at 1–2 outputs/day, with unlimited revisions, native source files, and full copyright/IP transfer on every plan. It is NOT a DIY tool you operate (Canva) and NOT a one-off logo service — it is how you HIRE OUT ongoing on-brand marketing creative (social, ads, web, illustration, motion, video) at volume. Use for how the request queue and daily-output throughput really work, picking a plan (shared-queue Advanced/Business vs dedicated-designer Assigned/Team, 1 vs 2 outputs/day), what files/ownership you get, turnaround and designer-swap issues, or whether it has an API (UI-only). Do NOT use to validate or name the idea (/sales-idea-validation, /sales-namelix), for a one-off logo (/sales-logonerds, /sales-hatchful), or DIY self-serve creative (/sales-canva)."
argument-hint: "[describe what you need help with in ManyPixels]"
license: MIT
version: 1.0.0
tags: [sales, branding, design, creative, platform]
---

# ManyPixels Platform Help

ManyPixels (**manypixels.co**) is a **flat-monthly, unlimited-request graphic-design subscription** —
"**design-as-a-service**." You pay a fixed monthly fee, submit **as many requests as you want**, and **human
designers** deliver **marketing creative** (social graphics, ads, landing pages, illustrations, motion/video, brand
assets, presentations) through a shared or dedicated queue. It is the **"hire out your ongoing design ops"** model —
the **human counterpart to a DIY tool like Canva** (`/sales-canva`): you don't operate an editor, you brief a designer.
It is **not** a one-off logo service (`/sales-logonerds`) and **not** a validation or naming tool.

**The first fact that frames every answer — "unlimited requests" ≠ unlimited *simultaneous* output; the queue is
SERIALIZED.** You can pile up an unlimited *backlog*, but designers work it **one active item at a time** (two on the
2-output plans). Real throughput = your plan's **daily-output count** (1 or 2 outputs/day), each turned around
next-day (shared queue) or same-day (dedicated). So the mental model is **unlimited in, one-or-two-at-a-time out** —
if someone expects to fire off 20 requests and get them all tomorrow, correct that first: they'll be delivered
**sequentially**, so **scope requests small and sequence them by priority**.

**The second fact — you pick on TWO axes: shared-queue vs dedicated-designer, and 1 vs 2 outputs/day.** Shared-queue
plans (**Advanced ~$699/mo**, **Business ~$1,199/mo**) are cheaper but **a different designer may pick up each
request** (less brand continuity, next-day turnaround). Dedicated plans (**Assigned Designer ~$1,399/mo**, **Design
Team ~$2,599/mo**) give you **one (or two) part-time designers who learn your brand**, **same-day** turnaround, and a
**timezone match** — at a premium. Every plan includes **unlimited requests + revisions + brands, licensed stock,
native source files, and full copyright & IP transfer**. All pricing is **best-effort → confirm at
manypixels.co/pricing** (quarterly ~10% off, yearly ~20% off).

## Step 1 — Gather context

If `references/learnings.md` exists, read it first for accumulated platform knowledge.

Ask only what you can't infer:

1. **What do you want from ManyPixels?**
   - A) **How the model works** (unlimited requests → serialized queue → daily-output throughput → revisions → files)
   - B) **Which plan / price** — shared-queue vs dedicated-designer, 1 vs 2 outputs/day, what each includes
   - C) **What files / ownership** you receive (native source files; full copyright & IP transfer)
   - D) **Turnaround & throughput** — how fast, and how much work you can actually get done per month
   - E) **Designer consistency** — the shared-queue designer-swap issue and when to go dedicated
   - F) **How it compares** — vs DIY (Canva), vs a one-off logo (LogoNerds), vs a contest (99designs/DesignCrowd)
   - G) **Automate / integrate** ("API" / bulk — see Step 4)
2. **Is the work ongoing marketing creative, or a one-off?** Ongoing volume of on-brand assets → ManyPixels; a single
   logo → `/sales-logonerds` or a DIY maker; DIY self-serve creative you make yourself → `/sales-canva`.

Skip-ahead: a *name* (not design) → `/sales-namelix`; the validate-before-building *method* → `/sales-idea-validation`;
a **one-off logo** → `/sales-logonerds` (human) or `/sales-hatchful` (free DIY); **DIY self-serve creative** →
`/sales-canva` — route in Step 2.

## Step 2 — Route or answer directly

| If the user's question is about… | Route to |
|---|---|
| Generating the **business name** itself (not the design) | `/sales-namelix {question}` |
| The validate-before-building **method** / branding-tool comparison across the market | `/sales-idea-validation {question}` |
| A **one-off custom logo** (human, done-for-you) | `/sales-logonerds {question}` |
| A **free/instant DIY logo** | `/sales-hatchful {question}` |
| **DIY self-serve** creative you make yourself (templates, Brand Kit, bulk-from-CSV) | `/sales-canva {question}` |

When routing, give the exact command: "This is a {domain} question — run: `/sales-canva {original question}`"

Otherwise, answer ManyPixels-specific questions using Step 3.

## Step 3 — ManyPixels reference

**Read `references/platform-guide.md`** for the full reference — the **unlimited-request → serialized-queue →
daily-output** model and how throughput really works; the **plan anatomy** (shared-queue vs dedicated, 1 vs 2 outputs,
what each tier includes) with the side-by-side table; every **service module** and its automation tag; **files &
ownership** (native source files, full copyright/IP transfer); the **design-as-a-service positioning** (vs DIY Canva,
vs a one-off logo, vs a contest); the **no-public-API** reality (and what the affiliate program actually is); and the
**image-generation-API workaround** for genuine programmatic/bulk creative.

Answer using only the relevant section — don't dump the full reference.

## Step 4 — Actionable guidance

- **Lead with the model: unlimited requests, but a SERIALIZED queue — throughput = 1–2 outputs/day, not "everything
  at once."** Correct the common misread up front: you can submit an unlimited *backlog*, but designers deliver **one
  active item at a time** (two on the 2-output plans), each next-day (shared) or same-day (dedicated). Tell users to
  **scope each request small and sequence them by priority** — a giant multi-part brief blocks the queue behind it.
- **Pick the plan on two axes and name the trade-off.** Shared-queue (**Advanced ~$699**, **Business ~$1,199**) is
  cheaper but **any available designer** may take each request → **less brand continuity**; dedicated (**Assigned
  Designer ~$1,399**, **Design Team ~$2,599**) gives **one/two designers who learn your brand**, **same-day**, and a
  timezone match. Need more *volume* → the **2-outputs/day** tiers (Business, Design Team). Flag every figure
  **best-effort → manypixels.co/pricing** (quarterly ~10% / yearly ~20% off).
- **On files & ownership: every plan includes native source files and full copyright & IP transfer.** You get editable
  **native source files** (not just flattened exports) plus licensed stock assets, and **full copyright/IP transfer**
  on delivered work — cleaner ownership than a shared-template DIY mark. State it plainly; if the work is a **logo**
  specifically, add the usual **trademark ≠ ownership** caveat and consider `/sales-logonerds` for a dedicated logo.
- **If brand consistency matters, steer them to a dedicated-designer plan — the #1 complaint is designer swaps.** On
  shared-queue plans a **different designer can pick up each request**, so brand voice drifts across deliverables. If
  they need a consistent look across many assets, recommend **Assigned Designer / Design Team** (one designer learns
  the brand) and tell them to **supply a brand guide / style references with every request** regardless of plan.
- **Set turnaround expectations honestly — the 1–2-day promise is per SIMPLE output.** Standard graphics hit next-day,
  but **complex illustration, motion/video, and multi-page assets extend the cycle**, and **revisions re-enter the
  queue**. Tell users to **front-load a specific written brief** (audience, style refs, colors, what to avoid) to cut
  revision rounds, since every round costs another turnaround slot.
- **There is NO public API — don't plan a pipeline around it.** ManyPixels is a **human-in-the-loop service** driven by
  a **UI request portal** (plus Slack/Google Chat for *communication*, not automation) with **no REST endpoints, no
  webhooks, no Zapier/Make, no MCP**. The **affiliate program** (Tapfiliate, ~15% first-year commission) is a
  **referral** program, **not** an automation API — don't invent endpoints. For programmatic/**bulk** creative
  generation, use an **image-generation API** and treat ManyPixels as the manual "hire a human" step.

If you discover a gotcha or tip not in `references/learnings.md`, append it there with today's date.

## Gotchas

*Best-effort from research (2026-07) — pricing/plan/turnaround terms move; verify at manypixels.co/pricing.*

- **"Unlimited requests" ≠ unlimited output — the queue is serialized.** You submit an unlimited backlog, but designers
  deliver **1–2 outputs/day** (your plan's rate), one active item at a time. Scope requests small and sequence them.
- **Two plan axes: shared-queue vs dedicated-designer, and 1 vs 2 outputs/day.** Advanced ~$699 (1/day, shared),
  Business ~$1,199 (2/day, shared, "72% pick this"), Assigned Designer ~$1,399 (1/day, dedicated, same-day), Design
  Team ~$2,599 (2/day, dedicated). All figures best-effort → manypixels.co/pricing.
- **Every plan includes native source files + full copyright & IP transfer + licensed stock + unlimited brands.**
  Cleaner ownership than a template DIY mark — but a logo is still not a registered trademark.
- **Designer swaps are the top complaint on shared-queue plans** — brand drifts across deliverables. Go
  **dedicated-designer** for consistency and attach a brand guide/style refs to every request.
- **Turnaround slips on complex work.** Next-day holds for simple graphics; complex illustration, motion/video, and
  multi-page assets take longer, and revisions re-enter the queue. Front-load a specific written brief.
- **NO public API, webhooks, Zapier/Make, or MCP.** Slack/Google Chat is for communication, not automation; the
  affiliate program (Tapfiliate, ~15% first-year) is referral, not an API. For bulk generation, use an image-gen API.

## Related skills

- `/sales-canva` — The **DIY self-serve** counterpart: templates, Brand Kit, and bulk-from-CSV you operate yourself (ManyPixels is where you **hire the work out** instead of making it). Includes a real Autofill API — the automatable path
- `/sales-logonerds` — A **one-off, done-for-you HUMAN logo** at a flat one-time fee — contrast with ManyPixels' ongoing monthly subscription for *all* marketing creative
- `/sales-hatchful` — A **free/instant DIY** logo maker — the go-to for a single free logo instead of a paid design subscription
- `/sales-namelix` — Generate the business name first (design is the hand-off from a locked name)
- `/sales-idea-validation` — The validate-before-building method and the full naming/branding landscape (validate and name before you subscribe to a design service; also covers ownership-vs-trademark)
- `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do -a claude-code`

## Examples

### Example 1: "ManyPixels says unlimited requests for $699 — can I get 30 designs done this week?" (the model)
**User says**: "It's unlimited requests, so if I subscribe can I submit 30 briefs and get them all in a few days?"
**Skill does**: Corrects the core misread — **"unlimited requests" means an unlimited backlog, not unlimited
simultaneous output**. On Advanced (~$699) designers deliver **1 output/day** (2/day on Business ~$1,199), **one active
item at a time**, so 30 briefs are delivered **sequentially over weeks**, not all at once. Advises **scoping each
request small and sequencing by priority**, and going to a **2-outputs/day** tier for more volume. Flags prices
best-effort → manypixels.co/pricing.
**Result**: The user plans realistic throughput and picks the right tier instead of expecting a batch overnight.

### Example 2: "Our logo keeps looking different across the graphics we get back — why?" (designer consistency / plan choice)
**User says**: "Every ManyPixels designer interprets our brand differently and the deliverables don't match. Help."
**Skill does**: Explains this is the **shared-queue designer-swap** issue — on Advanced/Business **any available
designer** can pick up each request, so brand voice drifts. Recommends an **Assigned Designer (~$1,399) or Design Team
(~$2,599)** plan where **one designer learns the brand** and delivers **same-day**, and — on any plan — **attaching a
brand guide + style references to every request**. Notes all plans include **native source files + full IP transfer**,
so the assets are yours to reconcile.
**Result**: The user switches to a dedicated plan (or standardizes the brief) and brand consistency improves.

### Example 3: "Is there a ManyPixels API so I can auto-submit design requests from our app?" (developer/automation)
**User says**: "Can I automate ManyPixels — an API/webhook to submit briefs and pull finished files programmatically?"
**Skill does**: States ManyPixels has **no public API** — a **human-in-the-loop service** driven by a **UI request
portal** (Slack/Google Chat is communication, not automation) with **no REST endpoints, webhooks, Zapier/Make, or
MCP**, so requests **cannot be scripted**; clarifies the **Tapfiliate affiliate program (~15% first-year)** is
referral, **not** automation, and doesn't invent endpoints. For programmatic **bulk** creative, suggests an
**image-generation API**, treating ManyPixels as the manual "hire a human" step.
**Result**: The user avoids building on a nonexistent API and picks a workable path.

## Troubleshooting

### "I submitted a big multi-part brief and nothing else is moving"
**Symptom**: One large request seems to block everything behind it in your queue.
**Cause**: The queue is **serialized** — designers work **one active item at a time** (two on 2-output plans), so a
sprawling multi-part brief occupies the slot until it's done, and a **revision re-enters the queue**.
**Solution**: **Split large briefs into small, independent requests** and **sequence them by priority** so quick wins
ship while a complex asset progresses. For more parallelism, move to a **2-outputs/day** tier (Business / Design Team).

### "Turnaround is slower than the advertised 1–2 days"
**Symptom**: Complex or multi-page work is taking longer than the next-day promise.
**Cause**: The **1–2-day turnaround is per simple output**; **complex illustration, motion/video, and multi-page
assets extend the cycle**, and each **revision round costs another turnaround slot**.
**Solution**: **Front-load a specific written brief** (audience, 2–3 style references, colors to use/avoid, where it'll
be used) to reduce revision rounds, and expect a longer cycle on complex assets. For same-day delivery, use a
**dedicated-designer** plan (Assigned Designer / Design Team).

### "I want to wire ManyPixels into our workflow with a webhook or Zapier"
**Symptom**: You're trying to trigger ManyPixels requests or pull finished files automatically.
**Cause**: ManyPixels is a **UI-only human service** — there is **no public API, no webhooks, no Zapier/Make, no MCP**;
Slack/Google Chat carry *communication*, not automation, and the Tapfiliate affiliate link is a referral program.
**Solution**: Handle requests and downloads **manually through the portal**. If you genuinely need programmatic/**bulk**
creative, use an **image-generation API** for the automatable portion and treat ManyPixels as the manual human step
for polished, owned deliverables. Verify current capabilities at manypixels.co before assuming any integration.