NašeApka

How We Work Together

First, we find out whether the problem is worth solving

The first step is simple: you describe the problem to us, and we assess whether it looks like a good fit for a customer portal, an internal tool, or automation.

We don't need a technical brief from you — we'll propose the type of solution based on the problem. We care that the result is simple to run and that the customer keeps control of their own data and source code. Long-term maintenance, monitoring, or ongoing development are separate arrangements, apart from the delivery price.

Send a problem for review
  1. 1

    Send us the problem

    Describe a process you currently handle manually, with a spreadsheet, e-mail, or an ill-fitting tool. You don't need a finished brief. It's enough to know what's slowing you down, where mistakes happen, and who at the company deals with it.

  2. 2

    We do a first assessment

    We check whether the problem is specific, repeats, and has a chance of making economic sense. If it already looks like a poor fit at first glance, we'll say so right away.

  3. 3

    We arrange a short, free call

    When it makes sense to continue, we go through the problem on a short call, typically under 30 minutes. The goal isn't to sell a large project, but to understand the process and decide whether it's worth a deeper, paid analysis.

  4. 4

    We prepare a paid analysis

    Suitable requests move on to analysis. There we clarify exactly what needs to change, how we'll recognize a finished solution, where the boundaries of the project lie, and whether the investment is likely to pay off for the customer.

  5. 5

    You decide on development

    After the analysis you have clearer grounds for a decision. If development doesn't make sense, it's better to find that out at this stage than after months of work.

  6. 6

    We deliver the solution

    Once you decide to proceed, we build the agreed tool, test it against the brief, and hand it over for use. The handover also includes a practical walkthrough of how to run the tool, who uses it, and what's needed for day-to-day operation.

  7. 7

    We handle fixes and adjustments

    After handover we offer a six-month warranty period, during which we fix bugs against the agreed brief for free. Smaller adjustments can be arranged on an ongoing basis; larger changes, new directions, or changes to operations need a separate agreement.

What we need from you

You don't need to design screens or a technical solution. It mainly helps us to know:

  • what exactly happens today
  • who's involved in the process
  • how often the work repeats
  • roughly how much time it takes
  • where mistakes or delays happen
  • who can decide on the next step

What you can count on

You're looked after by experienced developers who:

  • have practical experience in development, architecture, and real-world operations
  • understand how your company runs, not just the technology
  • assess whether a solution makes sense — before development even starts
  • don't build a bigger solution than the situation calls for
  • stand behind the result by name

Start by describing one specific piece of work

Pick a process that keeps slowing you down or where mistakes happen. Send it our way and we'll look at whether it's worth the next step.

Send a problem for review