Real estate · PropTech marketplace
Land-plot marketplace with a next-step plan: MVP in 2 months
From a mock-up to a working platform: plot → works → contractor → request. Rule-based next-step engine, three dashboards, personal-data compliance. MVP in 2 months.
- Status
- MVP in operation
- Timeline
- 4.5 months, MVP in 2
- Stack
- Python / FastAPI
- PostgreSQL + PostGIS
- React / TypeScript
- Redis
- Yandex Maps
- Docker / Traefik
The task
The client was launching a marketplace for land plots and the services needed to develop them. A buyer who finds a plot does not know which works are mandatory (title check, surveying, geology, utilities) and hunts for contractors by hand, while contractors get leads with no context. All that existed was a visual prototype: a map with filters, no backend, roles or requests.
What we built
- Built the full platform: backend, map with clustering and radius search, plot catalogue with filters and address geocoding. It runs in containers over HTTPS, and the live stand was updated with no data loss.
- A rule-based next-step engine at the core: from plot attributes, deal type and land category it returns a prioritised list of works, each with a stated reason. There is no ML, so rules change without retraining.
- Recommendations turn into a development plan with step statuses in one action. Contractors are matched by service and region; a request captures contacts and consent and notifies the company.
- Three dashboards (user, company, admin) with company verification and listing moderation. Personal-data compliance: consents and legal documents managed by admins, seller contacts hidden from guests.
- Laid the groundwork for importing plots from external sources (base importer, three adapter types, job log with deduplication); real sources are connected in the next phase.
Outcome
- 2 months
- from approved spec to a pre-release MVP on an HTTPS stand: week 9 against the plan’s own 10–13 week estimate
- 7 days
- from spec to the first full-implementation commit: 168 files, 21.5k lines, then two months of hardening to pre-release
- 93 endpoints · 26 tables · 19 screens
- MVP scope: 13 domain modules, 82 tests, 5 roles (three dashboard types plus moderator and super-admin)
- 11 rules
- in the next-step engine: a prioritised list of works, about 20 service types across 14+ categories, a reason for every recommendation
Services
More cases
Manufacturing · Building materials
MVP in operationPanel specs from CAD drawings in seconds, not hours
Reads DWG/DXF layouts and builds the Excel spec: 10–30 seconds instead of 2–15 hours by hand. All 784 panels of one real project matched the manual spec line by line.
- 784/784 and 189/189
- panels on one project and wall panels on another matched the manual specs line by line, size groups included; area within 0.001 m²
- 2–15 h → 10–30 s
- to produce a project spec: manual work vs app processing, measured on real projects
EdTech · HR-tech
MVP in operation (demo stand)From business canvas to a student-work marketplace demo in about six weeks
The client had a business model and no product. We built a student-task marketplace MVP where the server enforces legal and platform rules, and put a demo stand live.
- ~6 weeks
- from first commit to a deployed demo with all workspaces; 7 working days in commit history
- 3 checks
- run by the server before a contractor is assigned: data consent, self-employed status, mentor; each with a plain refusal
Marketplace e-commerce · Pricing
PilotRule-based repricing: a pilot whose contract terms are enforced in code
Competitor prices tracked per SKU, a price computed by rules inside an agreed corridor and applied only after confirmation. Pilot: 10 SKUs, setup within 14 days.
- 10 SKUs · 2 scenarios
- pilot scope; the SKU cap and both scenarios are enforced in code and verified by contract tests, so the cap cannot be exceeded
- up to 14 days
- contractual setup window from client inputs to launch, then a 1-month pilot; the service tracks the dates and closes access when the period ends
Estimate the payback of a similar process
AVA lets you work out the economics of your process on your own figures, with no form and no price from us. It shows what the manual work costs, what cash effect automation would give and what budget would pay back. If the effect does not even cover running costs, it says so.
Estimate the paybackDiscuss a similar problem
Describe the process and the data you have. Before any work starts we will tell you what can be measured in money, what cannot, and whether it is worth doing.