# Our Services

Through experience and failure, by observing and driving growth for various products, we’ve created battle-tested frameworks and processes tailored to different stages of product development. These theoretical models and real-world solutions are forged together, forming the base of our four core service lines. 

While following these practices is important, it is equally important, if not more, to question the purpose of each activity and understand how it ties into the larger goal. 

In a nutshell

[***Catalyse***](/what-we-do/our-services/catalyse-for-companies-looking-for-staff-augmentation-services.md): Work with conventions laid down by the customer to increase product development velocity.

[***Launch***](/what-we-do/our-services/launch-startups-and-early-stage-companies.md)*:*  Work with the customer to hit PMF

[***Control***](/what-we-do/our-services/control-fast-paced-tight-deadline-projects-with-moonshot-roi-potential.md): Work with enterprises on fast-paced tight-deadline projects with moonshot ROI.

[***Amplify***:](/what-we-do/our-services/amplify-scaleups-and-hyper-growth-companies.md) Work with a post-PMF customer (could be a previous Launch customer) and help them scale sustainably and profitably.

### Service Matrix

<table><thead><tr><th width="279">Activities</th><th align="center">Catalyse</th><th align="center">Launch</th><th align="center">Control</th><th align="center">Amplify</th></tr></thead><tbody><tr><td>Development, Automated tests</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Landscape Context</td><td align="center"></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Product Arch &#x26; Set up</td><td align="center"></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Agile Ceremonies</td><td align="center"></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Documentation &#x26; Reporting</td><td align="center"></td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td>App Modernisation</td><td align="center"></td><td align="center"></td><td align="center">X</td><td align="center">X</td></tr><tr><td>Audits</td><td align="center"></td><td align="center"></td><td align="center">X</td><td align="center">X</td></tr><tr><td>Systematise</td><td align="center"></td><td align="center"></td><td align="center"></td><td align="center">X</td></tr><tr><td>Intelligence &#x26; PLG</td><td align="center"></td><td align="center"></td><td align="center"></td><td align="center">X</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://playbook.wednesday.is/what-we-do/our-services.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.