Long-horizon business incubation and consulting

Operators

Operator roles

The roles WE places around your team, and where each one stops.

A dedicated team is made of roles

A dedicated team works only on your company and is made of defined roles. You choose the roles your company needs, and you can scale the team up or down by notice as the work changes.

WE steers the team and manages any subcontractors it uses. You deal with one team and not with a chain of vendors. The team is fully remote.

Roles, not individuals

This page lists functions. It does not name the people or firms who fill them, and it does not describe any person’s background. A role description tells you what to expect from the function and where it stops, so you can plan the rest.

The role list is the same list the Team Composer uses, so what you sketch there matches what is described here.

The nine roles

Product

Product design

Turns what customers told you into flows, screens and a design system the build team can use.

Engineering

Front end

Builds the parts of the product people see and use, in the browser and on small screens.

Engineering

Back end

Builds the services, data model and integrations behind the interface.

Quality and operations

Quality assurance

Plans and runs tests, records defects and checks each release against what was agreed.

Engineering

DevOps and security

Sets up the build, release and hosting routine and reviews the product for common security mistakes.

Brand and growth

Brand

Shapes the name, identity and the way the company describes its product.

Brand and growth

Growth and support

Runs customer discovery, pilots and a first support routine, and keeps the pipeline honest.

Quality and operations

Operations

Keeps the weekly rhythm: goals, metrics, reviews and the written record of decisions.

Delivery

Delivery lead

Plans each cycle with you, keeps the team on that plan and reports results in writing.

Where each role stops

Team roles, the service lines they mostly support and what each does not do
RoleMostly supportsDoes not do
Product designLine BDoes not decide what the product is for. That stays with the founder.
Front endLine BDoes not set product priorities or change scope without a written decision.
Back endLine BDoes not run your live product around the clock.
Quality assuranceLine BDoes not give any assurance that a product will pass an external audit.
DevOps and securityLine B, Line GDoes not certify the product and does not stand in for a specialist you hire.
BrandLine ADoes not give legal advice on names, marks or domains. Your counsel does that.
Growth and supportLine CDoes not close deals for you and does not promise that conversations become customers.
OperationsLine D, Line EDoes not keep your books, file your taxes or run the company for you.
Delivery leadLine A, Line B, Line C, Line D, Line E, Line F, Line GDoes not promise a delivery date or a funding result.

Service lines are described on the services page. Each line carries its own list of what it does not do.

Sketch the team you need

Choose roles in the Team Composer, or ask WE a question first.