BBlabBanja Luka Call

BBlabExamples: how the work usually goes

Most often you come to me with one of three things: an idea for an app, work that is run manually, or a team that keeps missing deadlines. Here is a description of what the path looks like in each of them.

Note. The three situations below are general examples.

Skica: tri različita početka, ideja, tabele i papiri, te razvojni tim, vode do istog cilja, posla koji radi ideja za aplikaciju tabele i papiri tim kojem bježe rokovi radi
The starting point differs, but the logic is the same: test on a small scale first, and only then invest more.

Finished products

Some of the products we have already built.

Situation 1

You have an idea for an app, and the budget can't go to waste

The idea sounds good, but you don't know whether people will actually use it. That's why we don't start with development but with validation: who is bothered by the problem and how they solve it today. Then I build a cheap prototype that real users can try, and you decide only after that.

If the idea turns out not to hold water, you found that out on a small scale, not after a big investment.

  1. Idea validationWhether the problem really exists and who it bothers.
  2. PrototypeA simple version that users try out.
  3. First productOnly what has proven to be needed.
Situation 2

The business runs on spreadsheets, paper and messages

Orders arrive in messages, records are in a spreadsheet, the rest is on paper. First I map out how the work really flows, step by step. The part that hurts the most gets digitized, and the rest only once the first part works properly.

Not everything changes at once, but piece by piece.

  1. Process overviewWhere time is lost on manual work.
  2. DigitalizationThe first spot that hurts the most.
  3. OptimizationLess manual work, with artificial intelligence where it makes sense.
Situation 3

You have a development team, but deadlines and costs are slipping away

The team is working, but there's no end in sight and costs keep growing. First I look at how the team works and where it gets stuck. Then comes a clearer order of work, development in smaller steps and mentoring until the team can take over on its own.

The goal isn't for me to stay forever, but for the team to carry on more confidently without me.

  1. Development process reviewWhere the work gets stuck and why.
  2. Team leadershipA clear order of work and smaller steps.
  3. MentoringThe team takes over and carries on by itself.

Sound familiar?

Tell me about your situation in a few sentences. If it doesn't look like any of these three, that's fine too, and we'll figure out where to start.

A message on Viber or WhatsApp is perfectly fine. You don't have to call right away.

Call BBlab