SoloEra solo activities, solo maxxing, sidequests, challengePhotograph the damage, know what it costs before you call
Talk to Gian@gianmauric
Reach out if you want to build it, build it together, or just ask what they had in mind.
01 The idea
A crack in the wall, a leaking pipe under the sink, a dented wing, a broken tile. Photograph it and get a realistic price range for the repair in your area, plus how urgent it actually is.
The problem isn't finding a tradesperson. It's that you have no idea whether the quote you're given is fair. Most people accept the first number because they have nothing to compare it against, and the ones who get three quotes lose a week doing it. Anyone who has been quoted for a car repair or a plumber knows exactly this feeling.
The urgency answer matters as much as the price. "This is cosmetic, it can wait a year" and "this is water damage, call someone today" are different lives, and right now people find out by panicking or by ignoring it too long.
Two hard parts.
Prices are regional and the data is nowhere. Trades don't publish rates, and what a job costs in Zurich is not what it costs two hours away. The honest version probably starts with ranges wide enough to be true and narrows as real invoices come in from users who report what they actually paid.
And there is a liability edge. Telling someone a crack is cosmetic when it's structural is not a bad recommendation, it's a dangerous one. Anything load-bearing, electrical or gas has to route straight to "get this looked at" rather than produce a number.
Generated build prompt
Your starting point. Copy it and start building.
Opens in your chosen app. Desktop app or sign-in may be required.
View full prompt
Build photograph the damage, know what it costs before you call. Context: A crack in the wall, a leaking pipe under the sink, a dented wing, a broken tile. Photograph it and get a realistic price range for the repair in your area, plus how urgent it actually is. The problem isn't finding a tradesperson. It's that you have no idea whether the quote you're given is fair. Most people accept the first number because they have nothing to compare it against, and the ones who get three quotes lose a week doing it. Anyone who has been quoted for a car repair or a plumber knows exactly this feeling. The urgency answer matters as much as the price. "This is cosmetic, it can wait a year" and "this is water damage, call someone today" are different lives, and right now people find out by panicking or by ignoring it too long. Two hard parts. Prices are regional and the data is nowhere. Trades don't publish rates, and what a job costs in Zurich is not what it costs two hours away. The honest version probably starts with ranges wide enough to be true and narrows as real invoices come in from users who report what they actually paid. And there is a liability edge. Telling someone a crack is cosmetic when it's structural is not a bad recommendation, it's a dangerous one. Anything load-bearing, electrical or gas has to route straight to "get this looked at" rather than produce a number. Requirements: - Ship the smallest version that delivers the core value above, nothing more. - Pick a stack you can deploy in a day, and state the choice before writing code. - Handle the empty state, the error state and the offline case explicitly. - Pricing to build toward: Free to check — that's the moment of need. Money comes from connecting to a tradesperson afterwards, which is also the conflict of interest: the price estimate has to stay honest even when a low estimate loses you the referral fee. State it openly or the whole thing is worthless. Start by listing the screens, then build them one at a time.