Case

ENEY MVP case: from name to live website

How we launched our own motor-launch website — from name, domain and identity to services, forms, sitemap, schema and Search Console.

Self-caseENEYMotor launchService + OfferSearch Console

ENEY MVP case: site structure, sitemap, schema, Search Console and live launch

Starting situation

ENEY didn't start with a long brief, but with a clear task: quickly build our own website that explains the motor-launch service, shows the service formats, accepts requests, and can be indexed by Google.

What we had at the start

the name ENEY
the domain eney.org.ua
the idea of “motor launch websites”
a dark visual identity
a lightning bolt as a symbol of speed, light and forward motion
a first site archive
the need to quickly assemble a public version

What needed to be built

a homepage
service pages
services as product-style pages with a “from” price
a request form
a case study
sitemap.xml
robots.txt
Google verification
Service + Offer schema
a responsive mobile/desktop experience

Key decisions

A dark identity and a real lightning bolt

Instead of a light site with a dark hero, a fully dark system: a graphite-blue background, white text, an electric blue accent. The lightning bolt sets the tone for the whole site, not just the first screen.

Services as product-style pages

Every launch format — Start Page, Business Site, Catalog MVP, Rebuild, Launch Pack — is presented like a product card: a “from” price, what's included, who it fits, and what affects the final price.

Service + Offer instead of Product

Services aren't physical goods, so for Google they're described through Service + Offer schema, not Product. Honest markup, without the risk of misleading anyone.

A 25 / 25 / 25 / 25 payment structure

Staged payments on every service page — a transparent system that protects both the client and ENEY, without final-stage risk for either side.

Mobile, not a squeezed desktop

A compact header with a burger menu, a hero built on svh/dvh units, safe-area handling for the browser's bottom bar — the mobile version was designed separately, not compressed from desktop.

Search Console and first indexing

The site was prepared for crawling: sitemap.xml, robots.txt, a self-canonical on every page, and ownership verification in Google Search Console.

What's already being indexed

Google already sees part of ENEY's key pages. The rest are being indexed gradually through Search Console and the sitemap.

What this case proves

This case isn't about making any website “in a hurry”. It shows something else: if structure, copy, design, forms, schema and launch move together in one process, a business can get a working digital form far faster than in the classic model with months of approvals.