EdTech · HR-tech
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.
- Status
- MVP in operation (demo stand)
- Timeline
- about 6 weeks, 7 working days by commits
- Stack
- Python / FastAPI
- PostgreSQL
- SQLAlchemy
- React / TypeScript
- OpenTelemetry
- Docker / nginx
The task
A regional operator of a student employment platform had a business model canvas but no product. Universities, a technology park and a government body needed to see a working flow: task, verified student, mentor, result, dispute with an SLA. Consent, self-employed status, mandatory mentoring and off-platform hiring protection had to be enforced by the server, not by policy.
What we built
- Built the platform from scratch: an async FastAPI backend on PostgreSQL and React/TypeScript workspaces. One codebase, infrastructure via docker-compose, Alembic migrations.
- The server enforces legal and platform rules. No contractor is assigned without data consent, self-employed status and a mentor on first tasks, and each refusal has a plain reason.
- Built an evidence layer: each work artifact is stored with a hash and a mentor seal, and a skill cannot appear in a profile without one. The database enforces this, so the interface cannot bypass it. Projects get a weighted 360° score.
- Closed the full loop: university verification, four organization types, service plans with SLAs, disputes with a server-computed deadline, ratings, and Git commits captured as work artifacts.
- Stood up a demo with admin, partner, company and mentor workspaces and demo flows for students, companies and the government partner. A canvas coverage map shows what is built and what is not.
Outcome
- ~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
- 7 of 7
- business canvas blocks covered by MVP modules; 4 gaps named explicitly in the coverage map
- 47 endpoints
- 21 tables and 21 screens: MVP scope counted from the code
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
Real estate · PropTech marketplace
MVP in operationLand-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.
- 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
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.