Sirotics Start a project
Work Capabilities AI Research Sectors Approach Insights About Start a project

Tell us the part
you're worried about.

The most useful first conversation is not about us. It is about the thing on your roadmap you are least confident in, and what it would take to settle it.

Booking discovery sprints now

We reply to every enquiry within two working days, including the ones where the answer is that we are not the right firm.

Start a project

Or just email hello@sirotics.com

We use what you send here only to reply to your enquiry. Nothing is shared with anyone else.


Other ways in

Registered office
124 City Road, London EC1V 2NX, England
Response time

Every enquiry gets a reply within two working days, including the ones where the answer is that we are not the right firm.

Under NDA already?

Say so and keep the detail out of the form. We will send a mutual NDA before the first call so you can speak freely on it.

Before you write

A few things
worth knowing.

Yes. A large share of first conversations happen before a budget exists, often the point of the conversation is to work out what the programme would actually cost so a budget can be argued for internally. We are happy to help shape that, and we will be specific about numbers.

Routinely. Send us yours or ask for our mutual NDA and we will have it back the same day. Do not put confidential detail in the form. A sentence about the shape of the problem is enough to get started.

No. Scoping conversations are free, including the follow-up ones. We start charging when work starts, and you will have a written scope and price before that happens.

That is usually the best way to start. A single feasibility question, an architecture review, a human factors study, a second opinion on a regulatory pathway: all normal first engagements. We would rather do one thing well than talk you into a programme.

Yes, and we do it often, usually where a specific capability is missing from an otherwise working team. What we will insist on is a single shared backlog and clear ownership boundaries. Parallel teams with overlapping scope create integration problems that look like schedule problems.