Kundcase
AI chatbot for geothermal permit applications
We built an AI chatbot for Herrljunga municipality that guides citizens through geothermal permit applications via chat, interactive maps, and automated geographic validation.
We build AI that is part of the product logic, automation that removes manual stops, and software your team can keep building on. From architecture to live in production — no handoffs mid-project, no transfer to someone else in the final week.
Software development
We develop applications that solve real problems for employees, customers and internal teams. That can mean an internal portal that removes manual work, a customer portal that improves self-service or a tool that makes data and workflows easier to manage.
We choose technology that makes the solution fast in production, easy to evolve and possible to integrate with the systems you already use.

Priorities
Not every idea needs to be built at once. We help you choose the initiatives that create the most impact based on processes, bottlenecks and business goals.
How we work
We start by understanding your goals, dependencies and biggest bottlenecks. Then we define a first step that can be introduced without creating unnecessary disruption in day-to-day operations.
The work happens in short delivery cycles with clear priorities and regular checkpoints. You continuously see what is being built, which decisions need to be made and what outcome we are aiming for next.

Risk and precision
The focus is on transparency, scope control and continuous validation. You should quickly be able to see what works, what needs adjusting and what the right next step is.

Vi arbetar med företag i olika branscher. Läs om tidigare projekt och vilka resultat lösningarna gav i praktiken.












FAQ
Common questions about how we prioritize, build and introduce solutions that create real operational impact.
It means we build for your specific workflow, not around a template. The result is a system that fits how your team actually works — with architecture that your developers can understand, extend, and maintain without calling us for every change.
Manual processes have a real cost: time spent on copy-paste between systems, errors that require rework, and workflows that break down when volume increases. The question isn't whether to automate — it's which process to start with and what a realistic result looks like.
It's what happens when you stop treating individual process improvements as isolated projects and start building toward a coherent system. That usually means better data quality, clearer ownership, and a roadmap — not just a series of one-off fixes.
We deliver in short cycles specifically because requirements shift. Each sprint produces something you can evaluate and redirect. We plan for change from the start — the architecture should make it easier to adapt, not harder.
⚡ We answer within 24h!