Torn between excitement and caution: how would you sanity‑check a solo‑dev SaaS before €10k?
I’m a non‑technical investor candidate wrestling with mixed feelings. I’ve been following a very young German property‑management SaaS built by a solo developer. In a few months they’ve shipped a surprising amount, and I keep seeing rapid improvements week to week. It’s honestly exciting and motivating — I’d like to contribute, be part of the effort, and help this become sustainable.
But here’s my dilemma: I can’t tell if I’m seeing true engineering quality or just impressive momentum. I don’t know how it will hold up under real‑world load, how thoughtful the architecture is, or whether security/GDPR and basic ops (backups, monitoring, recovery) are more than a checklist. Hosting is likely in an EU cloud; there are test users and first paying pilots on the horizon. I’m considering ~€10k, which is meaningful for me, and I really don’t want to confuse speed with durability.
If you’ve been in my shoes — founder, engineer, or investor — what are your highest‑signal, low‑effort ways to pressure‑test something like this , with or without code access? I’m looking for 2–3 practical moves or war stories that reveal “is this built to last?”
As a bonus: is a focused 1–2 day review by a senior engineer even feasible at a cost that’s proportionate to a ~€10k commitment? And if it is, would I need a German‑speaking engineer for this, or would an English‑speaking senior be just as effective for the assessment?
I’m not chasing perfection — I want to surface the big risks before I commit.