We started SIXSEVEN because the meeting kept happening.
In 2024 our founders were sitting in a room where eleven people spent ninety minutes agreeing that AI was important. Nobody said what for. Everybody left energised.
We built SIXSEVEN so that meeting could have an outcome — specifically, a vendor. Two years later that meeting happens at scale, in six regions, with an annual contract behind it. This is the transformation we set out to deliver.
Our technology is one model call, wrapped with care, governance, and an unusually good deck. We have never hidden this. It appears on slide four. Slide five is a chart, and everybody looks at slide five.
We are backed by investors who are also backed by investors, in a structure our CFO describes as “recursive but funded.”
The team
Photographs withheld pending a brand refresh that began in March.
Aleksandra Vance
Previously grew a category from zero to one. The category was hers. Speaks at conferences about the six months she does not discuss.
Tomás Ferreira
Wrote the wrapper. Maintains the wrapper. Has asked, in writing, that the wrapper not be called a wrapper.
Priya Nandakumar
Owns the 6/7 score. Determines the 6/7 score. Is benchmarked against the 6/7 score.
Bennet Krause
Renames the company internally every eleven weeks. Two of the names shipped.
Yuki Oyelaran
Wrote SOC 6.7. It is not a standard. It is not not a standard.
Oleg
Actually deploys things. Only person here with a laptop that gets warm.
github.com/swayoleg ↗67 open roles
Sixty-one are in go-to-market. We are aware. It has been raised.
| Role | Team | Location | Status |
|---|---|---|---|
| Forward Deployed Prompt Engineer | Delivery | Remote (CET ±0) | Open |
| Enterprise AE, Undisclosed Cycle | Sales | New York | Open |
| Category Narrative Lead | Marketing | London | Open |
| Head of 6/7 Methodology | Outcomes | Remote | Interviewing |
| Backend Engineer | Platform | Anywhere | Open (2 years) |
| Chief of Staff to the Chief of Staff | Executive | New York | Filled internally |