Tools we use — and why
The tool is chosen after the process, not before. Here are the platforms in our workshop and what we use them for.
The principle
The tool appears in the middle of the conversation, not in the headline of the offer. We don’t start with the platform — we start with the process. Only after the assessment do we know which tool fits a given workflow.
What’s in our workshop
Automation platforms
We use platforms that let us build workflows without writing code from scratch. Each has its place: one handles API integrations better, another handles document flows. The choice depends on the process, not our preference.
Browser (Falcon Browser)
Our own browser for monitoring and data collection. This isn’t a “bot” — it’s a tool that looks on behalf of the company: checks websites, gathers information, monitors changes.
Engine (Chaos)
The system that builds and maintains what we do. It manages deployments, tracks versions, ensures processes run without interruptions.
Knowledge bases
We build knowledge bases on foundations that already exist — we don’t create new ones from scratch. Every base has cited sources: where the information comes from and when it was collected.
What we don’t do
- We don’t choose the tool before assessing the process.
- We don’t show the tool name in the headline of the offer.
- We don’t promise that one tool will do everything.