Contact THE SHRIKS

Request access to the pilot, or write to us about the product, a partnership, a technical evaluation, or a press or research enquiry.

Request access to the pilot

A pilot runs SylvieSI on your real product, and you tell us what works and what does not.

Who it suits

A team that ships a web product and hears from users through your app, Slack or Gmail.

What you connect

At least one message source and read access to your code. Linear and Sentry if you use them. You choose each permission.

What happens next

We read your request, reply by email, and agree a plan with you before anything is connected.

What we ask

Tell us when SylvieSI is wrong, and review its results with us.

Email

What to include

Tell us about your team, the bugs and feature requests you handle, and what a good result would look like. Please do not include user data or credentials in a first message.

The form on this page prepares an email in your own mail application. It does not send anything to our website.

Prepare an email

This creates a draft in your email application. You send it yourself.

What to include in your message

A short, concrete description is enough to begin.

Product and partnership questions

Describe your team, the bugs and requests it handles, and what a useful result would be.

Technical evaluations

Name the tools and environment at a high level. Do not send credentials, API keys, production access or private user data.

Press and research

Include the topic, what you need, and any deadline.

Read the FAQ

About THE SHRIKS

SylvieSI is software from THE SHRIKS for teams that ship a web product. It has three parts. Mobius reads what users send from your app, Slack and Gmail, groups duplicates and gathers repeated requests into one Idea with the arguments for and against. Ouroboros takes a confirmed bug or an approved request, finds the cause, prepares the change and checks it on staging. Sylvie is the workspace where your team directs both. Ten AI agents do the reading and drafting. A person approves every change, nothing merges or deploys on its own, and the user hears back only after the fix has been checked. Pilot access is by request.