Requesters Providers

Creating A New Economy
for the Community

Shadow exists so that no task is too small to ask for, and no skill is too ordinary to be worth paying for. We're building a marketplace where real people solve real, everyday problems for each other.

Our Purpose

We believe that almost every day, someone runs into a problem that's too specific for an app, too small for a company, and too occasional to justify solving any other way. At the same time, almost everyone has spare time, local knowledge, or an everyday skill that's worth something to someone else. Shadow exists to put those two people in the same conversation.

A Request, Not a Category

Most platforms ask what kind of help you need: a delivery, a ride, a clean, a repair — and then fit your problem into whichever category comes closest. We think that's backwards. On Shadow, the request comes first. Whatever category it belongs to, if any, comes after.

A Platform, Not a Participant

Shadow connects people. It doesn't perform the task, set the price, or stand behind the outcome. Being honest about that, to ourselves and to everyone using Shadow, is what makes it possible to be fair when something doesn't go to plan.

Built for Both Sides

We try to make every decision, pricing, verification, reviews, support, with a Requester and a Provider both in mind, because Shadow only works if both of them do.


What We Stand For

  • 01 Describe the problem, not the category.

    The most useful thing about Shadow is what it doesn't ask you to do: pick a category before you've even explained what you need. If a request is lawful, safe, and genuine, it has a place here. However specific, occasional, or unusual it is.

  • 02 Ordinary ability counts.

    You don't need a qualification to be useful to someone else. Reliability, a spare afternoon, local knowledge, or simply being willing to show up are real value. We build Shadow so that value can become income, one at a time.

  • 03 Trust has to be built, not assumed.

    Identity checks, records, and reviews aren't paperwork. They're how strangers end up trusting each other enough to do business. We build these into Shadow because they protect Requesters and Providers in equal measure.

  • 04 Boundaries are part of the product.

    Shadow is the marketplace, not the employer, the guarantor, or the service itself. We try to be clear about that distinction everywhere, not as a disclaimer, but because it's what keeps the platform fair when something doesn't go as planned.

  • 05 The small stuff matters.

    A forgotten charger, a parcel stuck in a lobby, a pet that needs checking on, these are easy to wave off as too minor to bother with. We don't think they are. The small, in-between problems are exactly what Shadow is for.


How We Build

Shadow is shaped less by a fixed roadmap and more by what actually happens when a request meets an offer. A few things guide how we build it:

We choose the simple version first. A clear yes-or-no review tells a Requester or Provider more than a five-star average ever could, so that's the kind of review we built.

We change rules when they cause real problems for real people. Platform policy isn't fixed in stone; it gets revised when the gap between the rule and what's actually happening gets too wide.

We read both sides of every dispute. Not because every dispute is dramatic, but because the unglamorous edge cases are exactly where trust is either earned or lost.

We build for the next request, not just the current one. Shadow is meant to handle problems that don't exist as categories yet, so flexibility isn't a feature we added. It's a constraint we design around.


Shadow is for the people who'd rather ask than do without, and the people who'd rather help than scroll past. If that's you, on either side, this is what we built it for.