EcoplacesHospitality
Hotel booking platform, MVP in 3 months for a funding round
A booking site for country hotels and tours. As CTO, I hired two developers and built it with them on a small budget. The first version went live in 3 months, for the next funding round.

The founder had a budget for two developers and a funding round that needed a working product. Guests had to search, compare and book. Hotels had to confirm bookings without learning a new system. And hotel prices are not simple: seasons, weekends, extra guests, discounts and cancellation rules.
I chose the stack, hired the team and wrote code with them.
Most products I review were built fast on a small budget, like this one. I know which shortcuts are safe to keep and which must be fixed before a bigger test, because I took them myself.
The limits
Budget
Enough for two developers
Deadline
A working product before the next funding round
What the product had to do
For guests
Search, compare and book country hotels and tours
For hotels
Confirm bookings without learning a new system
For prices
Seasons, weekends, extra guests, discounts, cancellations
Safe shortcuts, and the ones I never take
A small budget means shortcuts. Some are safe to keep for years. Others turn into the problems I find in Reviews. Under each one: what I look for in your product.
Cut on purpose
No hotel owner app
Hotels confirmed, declined or cancelled a booking from secure links in an email. Nothing to install, nothing to support.
In your product I check
Which parts of your product nobody uses yet, but you still pay to maintain.
Do the guests fit the room?
Checked before the booking is created
Booking created
Emails go to our team and to the guest
The hotel gets an email with three secure links
No hotel app to build, host or support.
No online payments
Our commission was collected outside the site. No card data, no payment provider and no payment risk to manage.
In your product I check
Whether your product handles money or card data it does not need to.
No live room counts
A room was bookable when a price policy covered every night, minus blocked dates. The hotel confirmed the rest by email.
In your product I check
What your product promises users that it cannot actually check.
Two apps, not four
The guest site and the back office share one core and one database. Catalog, CMS and orders are parts of the back office, not separate systems.
In your product I check
Whether the same business rule is written twice, in places that can disagree.
Guest site
- Search and map
- Hotel pages
- Tours
- Booking
Back office
- Catalog and prices
- Orders
- CMS
- Reviews and import
One shared core, one database
Same data and rules, a schema per module
Not built, on purpose
Hotel owner app · Online payments · Live room counts
Never cut
Pricing rules as data
Seasons, weekday and weekend rates, extra guests, children, discounts, prepayment and cancellation rules. All set by the team in the back office, with no code change.
In your product I check
Whether a price or rule change needs a developer and a new release.
Set by the team in the back office
- Weekday and weekend rates
- Per room or per bed
- Extra guests
- Child discount, babies free
- Early-booking discount
- Long-stay discount
- Prepayment rules
- Cancellation rules
Price for the guest's dates
Worked out for every night of the stay
Bookable only if a policy covers every night, minus blocked dates.
Who can change what
Roles plus per-user permissions, tied to records such as orders. The back office API accepted only signed-in staff.
In your product I check
Whether admin pages are protected on the server, not just hidden in the menu.
One clear booking flow
Every booking had one status at a time, through 7 states from new request to commission received.
In your product I check
Whether an order can get stuck, or end up in two states at once.
A daily check on prices
A bot read each hotel's own website every day and flagged prices that no longer matched ours.
In your product I check
What tells you your data is wrong before a customer does.
A two-person team, a funding deadline
3 months
to MVP
12 months
to the full platform
2
developers I hired
2
apps to deploy and run
Requirements before code
The founder's ideas became tasks and screen mockups before anyone wrote code.
A hands-on CTO
I chose the stack, set the architecture, wrote code with the team and published every release.
Test, stage, production
Changes were checked on test and stage copies before guests saw them. Database changes went in as versioned migrations.
A small budget is not the risk. Shortcuts nobody wrote down are. In a Review, I list yours: which are safe to keep, and which to fix first.
What guests, hotels and the team got
For guests
- Search country hotels by region, dates and guests
- Results on a map, with an area filter
- Hotel pages with photos, facilities and driving directions
- Tours, booked the same way as stays
- Reviews with ratings for sleep, location, service and cleanliness
For hotels
- Booking requests by email, with secure confirm and cancel links
- Their prices kept by our team, and checked daily against their own site
- A contract with seasons, prices and commission terms
For the Ecoplaces team
- A catalog of hotels, rooms, photos and facilities
- Seasons, prices, discounts and policies
- Orders through 7 states, to commission received
- A lightweight CRM: customers, orders and newsletter sign-ups
- Homepage CMS and SEO landing pages
- Review moderation, and bulk import from CSV and Excel
Technologies
Application
Data
Back office
Delivery and services
What the client said
“It was a totally smooth experience, Michael made all the stuff needed thoroughly and on time, communication was easy and I can't remember any misunderstandings.”
“We worked together with Michael on a Startup called Ecoplaces - an aggregator of out-of-town resorts in Russia. His area of responsibility was 1) creation of overall IT-architecture, 2) full-stack development, and 3) hiring for IT positions. It was a totally smooth experience, Michael made all the stuff needed thoroughly and on time, communication was easy and I can't remember any misunderstandings. Michael is a real professional with a huge and diverse amount of experience. He will really empower your team if you need a Senior Full-Stack Developer or Team Lead.”
Is a deadlinecoming?
A round, an audit, a big customer, a vendor contract. Book a 30‑minute Risk Assessment Call. We go through who built your product, what must be ready before that date, and what breaks today.
Free. No preparation. You leave with your 3 biggest risks in writing, and an honest answer on whether a review is worth it now.
