S Labs
You already know the problem and need to see whether an approach works on your own data.
The same gate discipline as a Discover, on a shorter clock.
How it works
A scoped proof of concept of three to four weeks, run inside your environment, ending in a go or a no-go. You keep the findings either way.
- Scope
One problem and one success measure, agreed in writing before anything starts.
- Prove
Three to four weeks inside your controlled environment, on the data you make available.
- Decide
A go or a no-go gate, and the findings are yours whichever way it goes.
What it does today
- The offer is open now, and it is the one thing on these four pages you can buy today.
- Every proof ends in a written finding, including the ones that end in a no.
What we do not claim
- S Labs is not a product. It is a way of working, on a fixed clock.
- A proof of concept is not a production system, and four weeks hardens nothing.
- A go at the end is a decision to build, not a promise the build will succeed.
A good fit
- Teams who can name the problem and give access to real data in a controlled environment.
- Teams who would rather spend four weeks finding out than six months assuming.
Not a fit yet
- Teams still working out what the problem is. That is what a Discover is for.
- Anyone who needs the result running in production at the end of the four weeks.
How this differs from a Discover
A Discover diagnoses. You have a problem you cannot yet name precisely, and two weeks of paid work ends in a written diagnosis and a go or a no-go on building anything at all.
S Labs tests. You already know the problem, and somebody has already chosen an approach. Three or four weeks answers one question: does this approach work on your data, measured the way we agreed before anyone started.
If you are not sure which of the two you need, it is a Discover.
What you get
A written finding: what was tried, what the numbers were, and whether the approach holds. The code and the configuration from the proof. A recommendation that is allowed to be no.
What we need before the clock starts
One problem, written down. One success measure with a number in it, agreed in writing. Access to real data in an environment your security team is comfortable with. And one person on your side who can answer a question inside a day, because four weeks does not survive a week of waiting.
What happens at the end
A gate. Go means there is a measured result and a scope for what a production build would be. No-go means the approach did not clear the bar, and you found that out in four weeks instead of six months. The finding is yours either way, and you are free to hand it to somebody else.
We check the problem before anyone talks about a build.