FAQ
What you should know before we start.
What clients often ask before we get started. About AI, data, collaboration, and how we work.
AI, data, and control
Where does my data go when AI is involved?
That is defined before the project starts. Depending on the task, local models, cloud services with a data processing agreement, or a combination are used. You know exactly which services are involved and where data is processed before anything begins.
Can AI make decisions on its own?
No. Anything that triggers a consequence (sending, deleting, approving, paying) needs your sign-off. AI prepares, a person decides.
What does "local" actually mean?
The actual processing runs on your machine, server, or within your network. Which data the system is allowed to send externally is defined deliberately, not assumed by default.
What do you deliberately not automate?
Anything legally, financially, contractually, or personally sensitive is not automated blindly. The system can prepare, flag, or remind. The decision stays with you.
Collaboration and getting started
How does a typical project work?
You describe the process or idea. Together we figure out the smallest useful first step. No months of planning before something usable exists. The first step is scoped small enough to build cleanly and test in practice.
What does a project cost?
That varies as much as the projects themselves. A small automation can take a few days, an internal tool a few weeks. In the initial assessment you get a realistic sense of scope and effort, before anything costs money.
What do I need to get started?
A specific workflow or idea, two or three real examples, the tools you use today, and a sense of what should work better in the end. No technical knowledge required.
Why is this website so plain?
On purpose. Flashy effects are easy to build these days and prove little. This site should load fast, say clearly what Nori Works does, and let you read in peace: no tracking, no cookie banner. The systems built here follow the same principle, first the part that carries the day-to-day.
Operations, handover, and maintenance
Do you work with existing tools?
Yes, when it makes sense. Email, spreadsheets, CRM, accounting software, Notion, folder structures, existing data sources. Not everything needs replacing. Often the best solution is one that fits into what is already there.
Does my team need to use AI?
No. In many cases your team just sees a form, a dashboard, an approval step, or an email template. AI works in the background. What is visible is the result, not the technology.
What happens after handover?
You get a documented system you can run yourself. If questions come up or adjustments are needed later, I am reachable. But the goal is always: you are not dependent on me.
Can a first system grow later?
Yes. The first version is deliberately small, but not built as a disposable prototype. If it works in daily use, it can be extended, connected, or operated more cleanly.
Nori Works and how we work
Why one person instead of an agency?
Because you talk directly to the person who builds. Shorter paths, fewer misunderstandings, more honest assessments. For larger projects, I work with a network of experienced freelancers.
What if a project turns out not to be worth it?
Then I say so. If the initial assessment shows the effort does not justify the benefit, or a simpler path exists, that is exactly what you hear. An honest no is better than a project nobody needs.
Do you also build software without AI?
Yes. AI is a tool, not the point. When a problem is better solved with a clean database, a form, or a simple workflow, AI is not needed.
Do you have professional liability insurance?
Yes. Nori Works has professional liability insurance. The insurer is Markel Insurance SE; the policy is managed via exali AG. This is not a quality seal or a guarantee for a specific project, but it is a useful baseline for professional work.
Working together
Got a process that should run better?
Describe it in a few sentences. You get an honest take on whether it can become a working system, and what that would look like.