Try it: the assistant on this site →
The problem
A business owner can usually describe what is not working: orders get lost in the inbox, employees retype data, or the system stalls with a larger number of operations. But they do not have to know what information a contractor needs for a first assessment.
A long form shifts that effort onto the client. An exchange of questions by e-mail, in turn, can take several days. I needed something in between: as simple as a message, but able to ask about things that depend on the previous answer.
The solution
There are two equal routes on the site. The client can write directly or use the assistant. In the second option they describe the matter in their own words, and the system asks one question at a time.
Above all, the conversation puts in order:
- the current way of working and the place where the problem arises,
- the people who use the process,
- the systems in use and the kind of data,
- the scale of the repetitive work,
- the legal, security and deadline risks,
- the result by which the company will know the project has succeeded.
What happens in the background
Screening out junk messages first
A first, light model recognizes whether the message concerns the services. It does not talk to the client and does not assess the project. It only protects the system from simple abuse.
A conversation matched to the answers
The actual conversation is run by a more precise model. It does not ask again about information already given, and it can finish before the limit of 16 exchanges if the material is sufficient. The e-mail address is needed only so that I can come back with the next step.
A separate summary
At the end the system arranges the data in a fixed structure: the problem, the current process, the expected result, the systems, the constraints and the contact details. Thanks to this I do not have to reconstruct the key facts from a long transcript.
What the assistant deliberately does not do
- it does not pretend to be Artur,
- it does not give a price or a delivery date,
- it does not choose a technology after a few sentences,
- it does not require payment,
- it does not replace an audit of the code, the data or the documents.
In the end I am the one who decides whether the matter is ready to be quoted, or needs a conversation, a paid analysis or a small demo. That boundary is important, because the person responsible for the delivery should also answer for the promises made to the client.
Protection against abuse and losing a conversation
The system limits the pace of sending messages and the number of new conversations from one network address. A session has a set period of validity, and the record makes it possible to return to a conversation already started. Contact details are handled on the server side.
The result
The client does not have to know developers’ language or prepare an extensive document. Before my first reply I see not just a request for “automation”, but a description of the work, the people, the data and the expected change.
The greatest value is not the chat itself. It is the shorter route from an unclear symptom to an honest decision about what is worth doing next.