From the requirementto a working assistant.
I listen first. Then I say whether it can run locally, on what, and what I will not promise.
- The job
- Hardware
- Model
- Assistant
- Handover
Component
Who uses it
A specialist or a company
One person with their own practice is a different setup from a team that shares procedures.
The data stays
The assistant lives on your hardware. That is the reason anyone buys this.
Built for the job
A different specialist, a different company, a different setup. I don't sell one package off a price list.
Poland, then Europe
Polish language and Polish clients first. The rest of Europe once it works here.
Not for everyonewho wants "some chatbot".
This makes sense when
- you have work an assistant should repeat, and data you don't want to hand to a cloud vendor
- you are a specialist or a small company, not a department shopping for another slide
- you accept that quality depends on the job, the hardware, and the model, not on a promise on a website
What I don't do
- I don't upload your documents to someone else's API "just for a moment"
- I don't promise one assistant for everything
- I don't take a job that cannot actually be delivered on hardware you have, or are ready to buy
Tell me what the assistantshould do.
A few sentences is enough: who will use it, which data must not leave the company, what hardware you already have. I'll come back with whether it can run locally, and how.
Based in
Krakow, Poland
Off the clock
Market
Poland, then the EU
Shape
A setup, not a subscription
Data
Stays with you
Company
Firehorse IT Consulting