Sprawdź pomysł na biznes w dziesięciu pytaniach

Problem: 4/5, Solidnie (wysoka pewność)

Czy problem jest bolesny, częsty i pilny?

The text names a recurring cost: disputes over work done and late payments, both tied to invoicing a week after the job. That is weekly pain with a cash-flow cost, which matches the 4 anchor. It is not a 5 because the cost is described, not quantified; nothing says how often disputes happen or how much cash sits unpaid.

Dowody z tekstu pomysłu

invoice a week later, which means arguments about what was done and late payments

write hours in a notebook or a WhatsApp group

Przyjęte założenia

• Assuming a late invoice delays payment by one to three weeks for a crew that bills a few thousand EUR a month.

Pytania do odpowiedzi

• How many invoices a month end in an argument about scope?
• How many days late do customers pay on average?

Co podniosłoby ocenę

• Lead with the cash-flow number: days from job to money, before and after.

Klient: 5/5, Mocno (wysoka pewność)

Kto dokładnie kupuje, czy da się do niego dotrzeć, czy ma budżet?

A narrow segment, a named buyer who is also the user, and a concrete way to reach the first forty of them. Owners at this size already pay for phones, fuel and some software, so a monthly fee is within their budgeting. This matches the 5 anchor. The only open point is whether the forty owners are representative of the country.

Dowody z tekstu pomysłu

owners of small landscaping crews (2 to 8 people) in Poland

I ran a crew like this for six years and still know about 40 owners in my region

Przyjęte założenia

• Assuming the owner both decides and pays, which is normal at this size.

Pytania do odpowiedzi

• Of the 40 owners you know, how many still run crews of 2 to 8?

Rynek i moment: 3/5, Niejasno (średnia pewność)

Jak duży jest rynek i dlaczego teraz?

Bottom-up: assuming 20 000 crews of this size times 29 EUR times 12 months gives a ceiling near 7 million EUR a year, and a reachable 5 percent is about 350 000 EUR a year. That supports a small company, not a venture outcome. Why now is not stated; smartphones on site have been normal for years. The category is stable rather than growing. Score 3: real but not sized by the text.

Dowody z tekstu pomysłu

small landscaping crews (2 to 8 people) in Poland

29 EUR per month per company

Przyjęte założenia

• Assuming 15 000 to 30 000 landscaping businesses in Poland with 2 to 8 people; the text gives no count.
• Assuming 5 percent of them would adopt any app in two years.

Pytania do odpowiedzi

• How many landscaping companies of this size exist in Poland (GUS data by employment band)?
• What changed recently that makes owners want this now?

Co podniosłoby ocenę

• State the target: a lifestyle business at 300 crews, or a path to adjacent trades (cleaning, roofing) that lifts the ceiling.

Alternatywy: 4/5, Solidnie (wysoka pewność)

Co ludzie robią dziś i dlaczego mieliby zmienić?

The status quo is named precisely, and the switching reason is concrete: the invoice goes out the same evening with photos instead of a week later. Switching cost is low because the crew already takes photos on phones. The text does not name any competing app, which keeps this from a 5; the founder should check what the owners who already use software use.

Dowody z tekstu pomysłu

write hours in a notebook or a WhatsApp group and invoice a week later

Notebook, WhatsApp photos, invoice in a spreadsheet template a week later.

Przyjęte założenia

• From general knowledge: field-service tools (Jobber, Workiz) and Polish invoicing apps exist, but target larger teams or only the invoice step.

Pytania do odpowiedzi

• Which three apps have the owners you know tried and dropped, and why?

Co podniosłoby ocenę

• Position against the notebook, not against software: same-evening invoice with proof.

Monetyzacja: 4/5, Solidnie (średnia pewność)

Czy zapłacą, jak, i czy liczby się spinają?

Flat per-company pricing fits how a small owner budgets and avoids per-seat friction for a crew that changes size by season. Against the pain (late payments on thousands of EUR), 29 EUR is easy to justify. To replace one founder salary at about 4 000 EUR a month, roughly 140 paying companies are needed. The text shows no evidence that owners pay for software today, which caps this at 4 with medium confidence.

Dowody z tekstu pomysłu

29 EUR per month per company, flat

Przyjęte założenia

• Assuming a crew bills 5 000 to 15 000 EUR a month, so 29 EUR is under 1 percent of revenue.
• Assuming cost to serve is under 2 EUR a month per company (storage for photos, no model calls).

Pytania do odpowiedzi

• What do the owners you know pay today for any app or accountant tool?
• Would they pay yearly up front for a discount?

Co podniosłoby ocenę

• Test 29 EUR against 49 EUR with the first ten owners; the pain may support more.

Dystrybucja: 4/5, Solidnie (wysoka pewność)

Jak pierwsi klienci mają Cię znaleźć?

A named first channel the founder already has access to, matched to a cheap product: forty phone calls cost nothing. The second channel, a regional trade group, is plausible for the next hundred. What is missing is anything repeatable beyond the region: no search, referral or partner channel is named. Score 4.

Dowody z tekstu pomysłu

First channel: I will call them, then the regional trade group on Facebook

still know about 40 owners in my region

Przyjęte założenia

• Assuming the Facebook group has a few thousand members and allows posts from members.

Pytania do odpowiedzi

• Where do owners outside your region gather: national groups, suppliers, trade fairs?

Co podniosłoby ocenę

• Build a referral into the product: the owner's customer sees the photo invoice and asks who made it.

Wykonalność: 4/5, Solidnie (wysoka pewność)

Czy da się to zbudować, jak szybko i co jest ryzykowne?

The first slice is obvious: a timer per job, photo upload, and a PDF invoice sent by email. All of it is proven technology and cheap to build with coding agents. Risks are operational, not technical: Polish invoicing rules (numbering, VAT, the coming e-invoicing system) and offline use on site. Evenings-only pace is the main constraint, so the first version should skip accounting integration. Score 4.

Dowody z tekstu pomysłu

Stage: idea and a clickable prototype, evenings only

photographs the site before and after, taps start and stop per job

Przyjęte założenia

• Assuming a standard mobile stack with photo upload, a timer and PDF invoice generation; no AI needed for the core.

Pytania do odpowiedzi

• Have you checked what a compliant Polish invoice needs, including the national e-invoicing rules?
• Does the app need to work without signal on site?

Co podniosłoby ocenę

• Ship invoice as PDF by email first; integrate with accounting software only after ten paying owners.

Trwałość przewagi: 3/5, Niejasno (średnia pewność)

Co powstrzyma kopię przed wygraną?

Nothing stops a copy on day one. What can build over time: the history of photo-backed jobs per customer (a switching cost once a year of records is inside), and trust in a small niche that larger field-service vendors do not serve in Polish. Founder insight helps but is not a moat. Score 3: none yet, plausible later.

Dowody z tekstu pomysłu

I ran a crew like this for six years

Przyjęte założenia

• Assuming an AI-free product, so the vendor-feature risk is low; a generic field-service tool could still add a Polish invoice template.

Pytania do odpowiedzi

• What will the app know after a year that a new entrant would not?

Co podniosłoby ocenę

• Make the job history useful to the owner's customer too (a shared record), which raises the cost of leaving.

Dopasowanie założyciela: 4/5, Solidnie (wysoka pewność)

Dlaczego Ty, i czy masz czas oraz runway?

Six years of running the exact customer's business is the kind of insight the market cannot read in a blog post, and the owner network is an unfair advantage for the first sales. Time is thin, eight hours a week, but runway is a year without revenue, which covers validation. The gap is build capacity: the text never says who writes the code. Score 4.

Dowody z tekstu pomysłu

I ran a crew like this for six years

evenings only, no outside money

Clickable prototype, about 8 hours a week, can go a year without revenue.

Przyjęte założenia

• Assuming the founder can build or has a developer; the text does not say who makes the app.

Pytania do odpowiedzi

• Who builds the app, and how many hours a week can they give it?

Co podniosłoby ocenę

• Decide now whether to pay for a first build or partner with a developer for equity; eight hours a week is enough to sell, not to build and sell.

Ryzyka: 4/5, Solidnie (średnia pewność)

Prawo, regulacje, platformy, etyka?

Two risks matter. Invoicing is regulated in Poland, and the national e-invoicing system will change what a valid invoice is; the product must follow it or hand off to accounting software. Photos of private gardens and occasionally people raise GDPR questions, manageable with retention limits and consent in the terms. No platform dependency beyond the app stores. Nothing here stops the idea. Score 4.

Dowody z tekstu pomysłu

the owner gets a ready invoice the same evening

Przyjęte założenia

• Assuming Polish jurisdiction and the national e-invoicing obligation applying to small companies in the coming years.
• Assuming site photos may include people or private property.

Pytania do odpowiedzi

• Have you confirmed the e-invoicing timeline for companies of this size?

Co podniosłoby ocenę

• Delete or blur photos after a set period and say so in the terms.