Business plan

1.Executive summary

This plan raises a small round of around 400,000 SEK (≈ €35,000) from one or two known investors — a friend, a former colleague, or a business contact — on a straightforward SAFE or convertible. The money funds twelve months of focused, full-time founder runway and a single production host. The cap table stays simple: founder retains comfortably more than 90% on a fully-diluted basis, and grant / pre-seed optionality is preserved.

This is the path with the best balance of risk and dilution among the three. By year three the business is at ~3.6 mln SEK ARR, comfortably profitable, founder-controlled, and an attractive candidate for either continued bootstrapping or an upgrade to a proper pre-seed on materially better terms.

2.Company & founder

Structure

Vome will be incorporated as a Swedish aktiebolag (AB). The minimum share capital is 25,000 SEK (≈ €2,200), contributed by the founder. Sweden is the natural home: it is where the founder lives and works, the corporate-tax regime is straightforward, GDPR is the law of the land, and Stockholm is well placed for European customers.

The cap table is intentionally simple and the business is structured so it can succeed without relying on optimistic scenarios.

Founder

The founder is Andrew (Andy) Lyeklint Hancock, a 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. The current Vome stack — Flask portal, HAOS provisioning pipeline, WireGuard automation, the VomeSync companion integration, the Node/Redis service and the public website — is the founder's own work. The intent is deliberately conservative: keep the team small and the product focused, hire only when the work justifies it, and never over-promise.

3.Product

VomeHome — managed Home Assistant (lead product)

Each customer is provisioned an isolated HAOS virtual machine on Vome's infrastructure. A small adaptor in the customer's home (a tiny single-board device or an existing OpenWrt / GL.iNet router) holds a WireGuard credential and connects outbound to the host; LAN devices then become reachable to the hosted instance. From the customer's point of view, it is just Home Assistant: every integration, add-on and blueprint that works on a self-hosted instance works the same way here. No port forwarding is needed; the home network is never exposed to the public internet.

A core design goal is two-way portability. A self-hoster can use VomeHome as a hot-standby that boots from their existing backup; a hosted customer can migrate to a Pi/NUC at any time. We intend to make VomeHome the easiest place in the HA world to not stay forever.

VomeSync — companion concept (supporting role)

VomeSync is a small open-source HACS-style integration with a Node/Redis backend. It lets switches in different Home Assistant instances signal each other — useful for multi-property setups and optional community events. The source for the companion is on GitHub; the wider VomeHome source remains available to investors on request, under NDA, ahead of any public open-sourcing decision.

Roadmap product lines

• Boot-from-backup migration: bidirectional one-click migration between local HA and a hosted VM.
• Geo-distributed hosts: EU and UK regions first; further regions follow paying demand.
• Companion ESP32 devices: small, modestly priced Vome-branded sensors / actuators that "just work" with VomeHome.
• Adjacent platforms: the same hosting + tunnel architecture can later host OpenHAB, ioBroker or Domoticz instances for users of those platforms.

4.Market & opportunity

Home Assistant publishes anonymised analytics on its public dashboard. As of late 2025 the platform reports approximately 1.4 million active installations, supporting 2,500+ native integrations, with year-on-year growth comfortably above twenty per cent. The reported figure is the opted-in number, so the true user base is meaningfully larger.

The wider context is a global smart-home market that industry analysts size at roughly USD 100 bn and growing at low double digits a year through the decade. Most of that revenue accrues to closed ecosystems. Home Assistant is the standout open alternative; it has, until now, lacked a credible managed offering for users who don't want to host it themselves.

Sizing the addressable market

These numbers are deliberately conservative orientation rather than commitment. The business does not need to win the whole market — capturing a low-five-figure number of paying homes at ~1,400 SEK / year ARPU (≈ €120) produces a durable, profitable business at small scale.

5.Competitive landscape

The smart-home space splits along two axes: open vs. closed ecosystem and plug-and-play vs. self-assemble. Closed ecosystems (Apple Home, Google Home, Alexa, SmartThings, Hubitat, Homey) own the easy onboarding side; open platforms (Home Assistant, OpenHAB, ioBroker, Domoticz) own the integration breadth and control side. VomeHome targets the empty top-right quadrant — an open ecosystem that is also fully managed.

Nabu Casa is a complement, not a rival. They earn their revenue from self-hosters who need remote access; we serve people who'd rather not self-host at all, plus self-hosters who want a managed safety net. The two offerings sit on either side of the same gap.

6.Go-to-market

Initial channels

• Home Assistant community. The HA forum, r/homeassistant (~600k subscribers), HACS, and a handful of well-followed YouTube channels in the smart-home niche. This is where our customers already are.
• Open-source presence. The VomeSync companion stays public on GitHub. Contributions, issues and reviews build credibility before we sell anyone anything.
• Hardware partner channel. OpenWrt / GL.iNet / Beryl are commonly used as VPN gateways. We co-publish step-by-step setup guides, then explore lightweight bundling.
• Multi-property niche. Holiday-let owners (Airbnb hosts in particular) and small property managers are an underserved segment with clear willingness to pay.

Pricing

Annual plans receive roughly two months free. Pricing is anchored against Nabu Casa for self-hosters and against the loaded cost of running a dedicated server at home. The value proposition is "we take care of the bit underneath, and we make sure you can leave whenever you like."

7.Technology & operations

Architecture

Each customer's Home Assistant runs in an isolated HAOS virtual machine on a bare-metal hypervisor host. WireGuard handles the point-to-point tunnel between the VM and the home; nginx terminates TLS for portal and per-customer subdomains; Stripe handles billing; Auth0 handles identity. The VomeSync companion service is a small Node + Redis deployment. Operational tooling, runbooks, backup schedules and incident response are documented in the open-source repository's OPERATIONS.md.

Capacity assumptions

• A modern dual-CPU host with 256 GB RAM comfortably runs ~30–60 light HAOS VMs.
• Per-VM steady-state cost lands around 25–35 SEK / month (€2–€3) at three-quarters utilisation.
• Stripe + Auth0 + monitoring add roughly 5–7 SEK (€0.50) per paying customer per month.
• WireGuard adaptor cost (one-off, optional, recovered via small hardware margin or shipping fee).

Security & privacy

• One VM per customer; no shared HA processes.
• WireGuard tunnel is outbound-initiated from the home; no inbound ports on the customer's network.
• Per-instance backups, encrypted at rest, 7–14 day retention, off-host storage.
• GDPR-compliant: data minimisation, deletion endpoints, DPA available for business customers.

8.Funding & projections

Use of funds (400,000 SEK)

Three-year customer trajectory

Cap table impact

A SAFE for ~400,000 SEK with a sensible discount (20%) and post-money cap (e.g. 8–12 mln SEK) implies an effective stake in the 4–6% band when it converts. Founder retains comfortably more than 90% on a fully-diluted basis, with a 5–10% option pool reserved.

Milestones

Pros

• Founder can go full-time on Vome, doubling effective output.
• Cap table stays simple; preserves grant and pre-seed optionality.
• Twelve months is enough runway to reach product-market fit and revenue.
• Aligned investor (someone who knows the founder) eases reporting overhead.

Cons / risks

• If growth misses target, runway is tight — need a clear contingency plan.
• Friends-and-family investing has interpersonal risk; structure as a clean SAFE with proper paperwork.
• Slower than Plan C; if a competitor (e.g. Nabu Casa) launches managed HA, the lead window narrows.

9.Risks & mitigations

10.Contact

The fastest way to talk to us is by email at invest@vome.io. The demonstration is at staging.vome.io and sync.vome.io. The companion VomeSync source is at github.com/Vortitron/VomeSync; the wider VomeHome source is available to investors on request, under NDA. The slide-deck companion is at /pitch.

Detailed financial workings and operational documentation are available on request. We'd rather have a thirty-minute conversation than send a fifty-page model.

1.Executive summary

This plan raises an institutional or angel pre-seed round in the 1.15–2.9 mln SEK (€100–€250k) band, with a working mid-point of ~2 mln SEK (≈ €175k). The money funds two production hosts, multi-region from day one, eighteen months of focused founder runway, and a part-time second engineer from month six.

The faster operating tempo gives Vome a credible path from demonstration to a multi-thousand customer SaaS at ~11 mln SEK ARR by year three, with a clean cap table and a defensible position in the European Home Assistant hosting market. This plan accepts more dilution and reporting overhead in exchange for the resources to move quickly.

2.Company & founder

Structure

Vome will be incorporated as a Swedish aktiebolag (AB). The minimum share capital is 25,000 SEK (≈ €2,200), contributed by the founder. Sweden is the natural home: it is where the founder lives and works, the corporate-tax regime is straightforward, GDPR is the law of the land, and Stockholm is well placed for European customers.

The cap table is intentionally simple and the business is structured so it can succeed without relying on optimistic scenarios.

Founder

The founder is Andrew (Andy) Lyeklint Hancock, a 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. The current Vome stack — Flask portal, HAOS provisioning pipeline, WireGuard automation, the VomeSync companion integration, the Node/Redis service and the public website — is the founder's own work. The intent is deliberately conservative: keep the team small and the product focused, hire only when the work justifies it, and never over-promise.

3.Product

VomeHome — managed Home Assistant (lead product)

Each customer is provisioned an isolated HAOS virtual machine on Vome's infrastructure. A small adaptor in the customer's home (a tiny single-board device or an existing OpenWrt / GL.iNet router) holds a WireGuard credential and connects outbound to the host; LAN devices then become reachable to the hosted instance. From the customer's point of view, it is just Home Assistant: every integration, add-on and blueprint that works on a self-hosted instance works the same way here. No port forwarding is needed; the home network is never exposed to the public internet.

A core design goal is two-way portability. A self-hoster can use VomeHome as a hot-standby that boots from their existing backup; a hosted customer can migrate to a Pi/NUC at any time. We intend to make VomeHome the easiest place in the HA world to not stay forever.

VomeSync — companion concept (supporting role)

VomeSync is a small open-source HACS-style integration with a Node/Redis backend. It lets switches in different Home Assistant instances signal each other — useful for multi-property setups and optional community events. The source for the companion is on GitHub; the wider VomeHome source remains available to investors on request, under NDA, ahead of any public open-sourcing decision.

Roadmap product lines

• Boot-from-backup migration: bidirectional one-click migration between local HA and a hosted VM.
• Geo-distributed hosts: EU and UK regions first; further regions follow paying demand.
• Companion ESP32 devices: small, modestly priced Vome-branded sensors / actuators that "just work" with VomeHome.
• Adjacent platforms: the same hosting + tunnel architecture can later host OpenHAB, ioBroker or Domoticz instances for users of those platforms.

4.Market & opportunity

Home Assistant publishes anonymised analytics on its public dashboard. As of late 2025 the platform reports approximately 1.4 million active installations, supporting 2,500+ native integrations, with year-on-year growth comfortably above twenty per cent. The reported figure is the opted-in number, so the true user base is meaningfully larger.

The wider context is a global smart-home market that industry analysts size at roughly USD 100 bn and growing at low double digits a year through the decade. Most of that revenue accrues to closed ecosystems. Home Assistant is the standout open alternative; it has, until now, lacked a credible managed offering for users who don't want to host it themselves.

Sizing the addressable market

These numbers are deliberately conservative orientation rather than commitment. The business does not need to win the whole market — capturing a low-five-figure number of paying homes at ~1,400 SEK / year ARPU (≈ €120) produces a durable, profitable business at small scale.

5.Competitive landscape

The smart-home space splits along two axes: open vs. closed ecosystem and plug-and-play vs. self-assemble. Closed ecosystems (Apple Home, Google Home, Alexa, SmartThings, Hubitat, Homey) own the easy onboarding side; open platforms (Home Assistant, OpenHAB, ioBroker, Domoticz) own the integration breadth and control side. VomeHome targets the empty top-right quadrant — an open ecosystem that is also fully managed.

Nabu Casa is a complement, not a rival. They earn their revenue from self-hosters who need remote access; we serve people who'd rather not self-host at all, plus self-hosters who want a managed safety net. The two offerings sit on either side of the same gap.

6.Go-to-market

Initial channels

• Home Assistant community. The HA forum, r/homeassistant (~600k subscribers), HACS, and a handful of well-followed YouTube channels in the smart-home niche. This is where our customers already are.
• Open-source presence. The VomeSync companion stays public on GitHub. Contributions, issues and reviews build credibility before we sell anyone anything.
• Hardware partner channel. OpenWrt / GL.iNet / Beryl are commonly used as VPN gateways. We co-publish step-by-step setup guides, then explore lightweight bundling.
• Multi-property niche. Holiday-let owners (Airbnb hosts in particular) and small property managers are an underserved segment with clear willingness to pay.

Pricing

Annual plans receive roughly two months free. Pricing is anchored against Nabu Casa for self-hosters and against the loaded cost of running a dedicated server at home. The value proposition is "we take care of the bit underneath, and we make sure you can leave whenever you like."

7.Technology & operations

Architecture

Each customer's Home Assistant runs in an isolated HAOS virtual machine on a bare-metal hypervisor host. WireGuard handles the point-to-point tunnel between the VM and the home; nginx terminates TLS for portal and per-customer subdomains; Stripe handles billing; Auth0 handles identity. The VomeSync companion service is a small Node + Redis deployment. Operational tooling, runbooks, backup schedules and incident response are documented in the open-source repository's OPERATIONS.md.

Capacity assumptions

• A modern dual-CPU host with 256 GB RAM comfortably runs ~30–60 light HAOS VMs.
• Per-VM steady-state cost lands around 25–35 SEK / month (€2–€3) at three-quarters utilisation.
• Stripe + Auth0 + monitoring add roughly 5–7 SEK (€0.50) per paying customer per month.
• WireGuard adaptor cost (one-off, optional, recovered via small hardware margin or shipping fee).

Security & privacy

• One VM per customer; no shared HA processes.
• WireGuard tunnel is outbound-initiated from the home; no inbound ports on the customer's network.
• Per-instance backups, encrypted at rest, 7–14 day retention, off-host storage.
• GDPR-compliant: data minimisation, deletion endpoints, DPA available for business customers.

8.Funding & projections

Use of funds (mid-point: 2,000,000 SEK)

Three-year customer trajectory

Cap table impact

A pre-seed round at this scale typically takes 10–18% of the company on a SAFE with a post-money cap. Founder retains majority control comfortably, with a 10% option pool reserved for the second engineer and any later hires.

Sensitivity

The dominant levers are customer count and blended ARPU. At half the customer count, break-even slips from year two to year three; at twice the customer count, the business is clearly profitable in year two. The capital required to survive the slower scenario is the same ~2 mln SEK round described above — which is the point: this round funds the conservative case, not the optimistic one.

Milestones

Pros

• Multi-region hosting from day one; better resilience and lower latency for customers outside the home region.
• Second engineer accelerates the boot-from-backup feature and reduces single-person risk.
• More marketing reach in the formative twelve months.

Cons / risks

• Higher dilution and more reporting burden than Plans A or B.
• Longer fundraising cycle (likely 3–6 months).
• Implicit pressure to grow faster, which can pull product priorities away from the durable, customer-friendly path.

9.Risks & mitigations

10.Contact

The fastest way to talk to us is by email at invest@vome.io. The demonstration is at staging.vome.io and sync.vome.io. The companion VomeSync source is at github.com/Vortitron/VomeSync; the wider VomeHome source is available to investors on request, under NDA. The slide-deck companion is at /pitch.

Detailed financial workings and operational documentation are available on request. We'd rather have a thirty-minute conversation than send a fifty-page model.