Where to focus first?

Working document for an advisor meeting · 2026 · Confidential, single-page print intended.

Brief context. One founder in Skåne (Andrew "Andy" Lyeklint Hancock — full-stack engineer) currently working on a managed Home Assistant service. Alongside that, I personally own a disused Swedish cinema I'd like to bring back into use as a flexible venue for hire — and the booking / automation system that runs it could itself be a small SaaS. So there are two distinct ventures sharing one founder and one technical platform, and a decision to make about which to lean into first. Positioning note: the venue / hire side deliberately aims at the less-corporate end of the market — small businesses, freelancers and work-from-home users, artists, weddings and private events — rather than chasing the enterprise / corporate hire that the Skedda-shaped tools already serve.

1.The shape of what's in front of me

SaaS side (Vome AB) Venue side (Nyvyn) Ownership / structure Customer relationship

2.Each piece, in one sentence

For each product: a hook line first (what it is at a glance), then the plain-words detail. The legal entity and the founder skip the hook and go straight to the plain version.

VomeHomeLead product · MVP ready: Hosting for Home Assistant. Like Squarespace for a self-hosted blog — same software the enthusiasts run, but you don't keep the server in your cupboard. A managed Home Assistant instance per household; subscription 89–349 SEK/month; customer keeps the full HA experience without buying or maintaining a home server, and can always move back to local hardware.
VomeHireSecond product · MVP to build: An automated Airbnb for function rooms. Like Skedda for the calendar, plus the lock, the lights, the projector and the coffee machine, all driven by the booking. A booking and operations SaaS for small venue owners; deliberately aimed at the less-corporate end (small businesses, freelancers, artists, weddings and private events) rather than the enterprise meeting-room market.
NyvynThe cinema · separate trading name: Bygdens egen biograf, för uthyrning. Like the village hall, but with a four-metre screen and the heating switched on by the booking. The disused single-screen cinema, brought back into use as a flexible venue for hire — held personally (likely as an enskild firma) so property-flavoured grants can fund the building work without entangling them with the SaaS.
VomeSyncOpen-source companion · already built: A bridge between Home Assistants. Like an intercom for separate homes — a switch in one house can signal a switch in another. A small open-source HACS integration plus a Node/Redis service. Useful for multi-property setups, valuable as brand and goodwill in the HA community; not a direct revenue line.
Vome ABLegal home for the software side: A Swedish aktiebolag, currently in formation. Owns the three software product lines above, contracts directly with customers, and is the entity through which any equity investment would flow.
FounderSolo for now: Andrew (Andy) Lyeklint Hancock — full-stack engineer based in Örkelljunga, Skåne, with a long background in PHP, Python/Django, Angular, Linux and AWS work (open-source as @adlh on GitHub). Built the existing Vome stack and personally owns the cinema.

3.What to focus on first — trade-offs

Four candidates for "where the founder spends most of the next six months." None of them is wrong; each has a different shape. The pros and cons below are deliberately structured the same way so they're comparable on the page.

Option A

VomeHome first

Quietly turn on the existing managed-HA service, get the first hundred customers, and let revenue from that fund everything else.

Pros

MVP is already built — weeks to launch, not months.
Recurring SaaS revenue is the friendliest story for any later raise.
The HA community exists; customer acquisition channels are real and free.
Customer 100 costs the same to onboard as customer 1.
Doesn't require the cinema to be ready.
Reuses every line of the existing engineering work.

Cons

Modest margin per customer (89–349 SEK/mo) — needs volume.
Crowded mindshare: HA enthusiasts often prefer to self-host on principle.
Always-on expectation: an unreachable home on a Sunday evening is a support escalation, not a Monday task.
Doesn't move the cinema forward at all.
Marketing-heavy: needs content, community presence or modest paid ads to grow past friends and the HA forum.
The first €100k of revenue takes longer than it looks on a spreadsheet.

Option B

Nyvyn first (the cinema)

Get heat in the building, open it for hires with a manual workflow, and let the real venue drive what VomeHire ends up being.

Pros

Tangible. Easy to explain to non-tech advisors, neighbours and grant-bodies.
Generates cash from real bookings even with a hand-rolled spreadsheet.
Forces VomeHire to be useful — real-customer discipline beats guesswork.
Property-flavoured grants (local development, energy retrofit) available without giving up equity.
Visible local presence: word of mouth in a small town beats Facebook ads.
Creates photos, video and a case-study for VomeHire's later sales.

Cons

Higher upfront cash requirement (~220–350k SEK to open responsibly).
Property-running risk: heating quotes creep, licences, insurance, fire-safety.
Geographic ceiling: one venue, one town, until VomeHire goes broader.
Slower to "scale" in the startup sense — it's a small business until VomeHire catches up.
If the engineering side is starved, VomeHire's launch slips and the showcase remains a hand-rolled spreadsheet for longer.
Bookings cluster on evenings and weekends; founder personal time is part of the cost.

Option C

VomeHire first

Build the SaaS to a sellable state, line up two or three friendly Swedish venues as paid pilots, and use Nyvyn only as the in-house showcase once it's warm.

Pros

Higher ARPU than VomeHome (~500–2,000 SEK/mo per venue), so fewer customers needed.
Less crowded than the HA niche: Skedda owns calendars but no one's doing packages + automation.
Sticky once installed — locks, AV and calendars are real switching costs.
The less-corporate positioning is differentiated and warm to sell.
Reuses the existing Vome portal / Stripe / Auth0 / HAOS stack.

Cons

MVP isn't done — weeks to months of build before the first sale.
Each venue is a small custom install (locks, AV, HA box). Onboarding is heavier than VomeHome.
Smaller TAM than VomeHome (tens of thousands of venues vs millions of households).
Hardware involvement brings field-support risk.
Without a visible reference venue (Nyvyn open), the cold sale is harder.

Option D · unlikely first focus

VomeSync first

Polish the open-source companion, build community goodwill, and use that as the inbound channel for whichever revenue line gets prioritised next.

Pros

Already mostly built — almost free to maintain.
Brand-building: GitHub stars, HA-forum credibility, inbound contacts.
Could open partnership conversations (Nabu Casa, HA Partner Program).
Compounds quietly alongside whatever the main focus turns out to be.

Cons

Produces no direct revenue.
Hard to fund: an OSS-first lead is a tough pitch to most investors.
Time spent here is time not spent on a revenue line.
Doesn't help the cinema get warm.

How they interact (worth raising with the advisor)

Nyvyn first → VomeHire follows naturally. The cinema's needs dictate what the SaaS must do, and the cinema's photos sell it to other venues.
VomeHire first → Nyvyn opens more smoothly but takes longer to first revenue, because the cinema sits cold while the software is built.
VomeHome first → almost no effect on the venue line. The platform DNA is shared, but the customer base is entirely separate.
VomeSync alongside any of the above is fine; on its own it isn't a first focus.
Funding mix is genuinely different per option. Property grants and Almi mikrolån suit Nyvyn-first; a small friends round suits VomeHire-first; VomeHome-first can probably bootstrap from existing engineering time.

What I'd most like the advisor's view on

Which of A, B, C should be the first six-month focus — given my background, the Skåne-region context, and what they've seen work for other small-but-serious Swedish founders.
Which Swedish funding instruments actually fit — Almi mikrolån, Vinnova Innovativa start-ups, EU local development for the cinema, anything else worth applying for in parallel.
Whether Nyvyn should sit inside Vome AB or trade separately from day one (current assumption: separately, but happy to be talked out of it).
Anything obvious I'm missing — a hidden cost, a regulatory tripwire, a sequencing trap, a much better partnership angle.
An introduction to one or two people who've done something nearby (small managed-service founders; small venue operators; people who've taken Almi or Vinnova money).