Ignition Labs · Business apps and AI solutions, built in Slovakia

    From idea to a first working version in 21 days.

    For small and medium-sized companies we design and build internal business apps, MVPs and AI automations – replacing Excel, tracking orders, approvals, connecting systems. The scope, price and deadline of the first version are agreed in writing up front.

    The 21-day timeline applies to a scope of the first version agreed in advance. Larger projects are split into stages.

    • More than 10 years of technology experience
    • Production systems used by hundreds of clients
    • Founder-led development with direct oversight
    Illustration of a rocket ready for launch
    Illustration of a robotic assistant

    What do you need to bring to life?

    These are the types of solutions we can build. The exact scope always depends on what you need to solve.

    Ladislav Mathis, MBA — Founder, Ignition

    Ladislav Mathis, MBA

    Founder, Ignition

    MBA in Mastery of AI

    Every Ignition project receives direct founder oversight — from understanding the problem and designing the solution to handing it over.

    Depending on the nature of the project, the Ignition team and specialists in individual technology areas contribute to delivery.

    LinkedIn profileDiscuss my project
    Who is behind Ignition

    Ignition is a new brand. The experience of the people behind it is not.

    Ignition is led by Ladislav Mathis, MBA and his team.

    More than ten years of experience with technology, products and real-world operations — from technical roles to development leadership and technology management.

    Ignition builds on a decade of hands-on technology practice — from technical roles through sales, product and project management to development leadership and technology management.

    The last three years have focused primarily on leading development initiatives, building technology products, product and project management, and development coordination.

    This professional journey also includes co-founding EasyKasa and working on solutions across POS, payments, eKasa, cloud services and system integrations.

    Product and technology direction is under direct founder oversight. Depending on the nature of the project, the Ignition team and specialists in individual areas contribute to delivery.

    The experience Ignition is built on

    01

    Technical foundations

    Practical experience with technology, devices and how they work in real-world operations.

    02

    Product and projects

    Connecting the needs of customers, business and technical teams from the first brief to product deployment.

    03

    Development leadership

    Three intensive years leading development initiatives, designing solutions and coordinating development.

    04

    Technology leadership

    Experience in product technology direction, architecture, integrations and CTO-level decision-making.

    Areas of experience

    Product & Project Leadership

    From understanding the problem and designing the product through development coordination to deployment.

    POS, Payments & Fiscal Systems

    Hands-on experience with POS systems, payments, the eKasa environment, devices and their integrations.

    Cloud & Integrations

    Cloud services, APIs, device communication and connecting systems that have to work as one whole.

    AI & Automation

    AI-assisted development, agentic workflows and process automation with a focus on practical use.

    We use AI as a tool to speed up our work. Solution design, technology decisions and accountability remain with people.

    What we are already building and operating

    Not demo projects for a slide deck, but technology we use, test or operate. Some already run in real-world operations, others are used internally or technically tested ahead of a pilot.

    What these projects say about how we work

    We work with both software and physical devices.

    We connect systems that were not originally designed to work together.

    We operate cloud services in a real production environment.

    We use AI for more than code generation — we build agentic workflows and automation on top of it.

    We test proofs of concept on real hardware and across different technology combinations.

    We clearly distinguish between a prototype, POC, pilot and production operation.

    For us, a proof of concept is not a screenshot. It is a working solution we can connect, test and demonstrate on a real system.

    For every project, we openly state what already runs in production, what we use internally and what is still being tested.

    How the process works

    Four steps from the first conversation to delivery of the first working version.

    STEP 1

    We clarify the goal

    We go through the problem, the users and the outcome the first version should deliver.

    STEP 2

    We agree on scope and price

    We define what will be part of the first version, what stays for later, and how delivery will work.

    STEP 3

    We build and show progress along the way

    We go through the development together so that unclear points and feedback can be caught early.

    STEP 4

    We test and hand it over

    We verify the agreed user scenarios and prepare the handover according to the agreed scope.

    Scope and price

    We have no flat price list. The price follows the scope we define in step two.

    • Interface design based on the way you work
    • App development including deployment to production
    • Usability on both mobile and desktop
    • Handover within the scope agreed in writing

    You receive the exact price, timeline and handover terms in a proposal before work begins.

    How we think about development

    Practical lessons from products, integrations and AI that we build and use ourselves.

    mission-logs.sh
    $ ls -la /all-logs▋

    What people ask us most often

    What does a "first working version" mean?
    It's an app in which the main scenario we agreed on actually works — the thing the user really needs to be able to do. It's not a finished product with every feature; we add further parts once we see how the first version is being used.
    When does the 21-day deadline apply?
    It applies to the scope of the first version that we agree on in writing beforehand. If it turns out during preparation that the scope is larger, we split the work into stages and agree a deadline for each one.
    How is the price determined?
    We only set the price after we've defined the scope of the first version together. So it comes from the specific brief, not from a price list. You'll get the exact price and payment terms in a proposal before work begins.
    Who will work on the project?
    Ignition works as a founder-led team. Product and technology direction is led by Ladislav Mathis, MBA, who has more than ten years of experience in technology. Depending on the project, his team and specialists in individual areas contribute to delivery.
    Can you automate a process using AI agents?
    Yes. We design agentic workflows and automations for clients, and we use our own agents daily in our work. For every deployment we define what the agent may do on its own and what goes to a human for approval.
    Do you also build integrations into existing systems?
    Yes, connecting systems, devices, payments and cloud services is one of our core areas. What is possible depends on the interfaces and access the given system provides.
    What do you need from me before we start?
    A description of the problem you're solving today, an idea of who the app should serve, and someone on your side who can answer questions about scope. If you already use some tools or have materials, it helps to give us access to them.
    How are new requirements handled during development?
    We note them down and decide together whether they belong in the first version or in a later stage. If a request changes the agreed scope, we agree a deadline and price for it before we start working on it.
    What do I get at handover?
    A working app according to the agreed scope, and an overview of how it is used and where it is deployed. The scope of the handover — i.e. exactly what you get, including access and code — is always agreed in writing before work begins.
    What running costs might arise?
    The app needs to run somewhere and often uses third-party services — hosting, a database, email or AI services, or domains. These costs are billed according to the relevant providers' prices and depend on usage. You will get a specific estimate when we agree on the scope.
    What happens after handover?
    Either we continue with another stage based on what real usage shows, or you take over the app and develop it yourselves. The scope of any further support is agreed separately.

    Have a project or a process you want to put into practice?

    Tell us what you need to solve. Together we will go through the scope of a first version that makes sense.

    Who should this solution serve, what do you do today, and what should change?

    You do not need a technical specification to start.

    Or write to us directly at info@ignition.sk, or call 0914 600 810.

    Illustration of a friendly alien