Talvio

Skills and services marketplace app: requirements, documentation and design

Talvio lets anyone list a skill with a price, take bookings, sell courses, and share their work, with chat, disputes, and payments built in.

Book an intro call See the deliverables

Product name and branding changed to protect client confidentiality. Our role: discovery, requirements, documentation and design. We did not build it.

Screens designed: 185
Platform: iOS, Android and iPad
Market: Content needed: country or region
Languages: 4

Overview

Talvio connects people who offer a skill, from graphic design to tutoring, with people who want to book them. Providers list skills with a fee and description, manage bookings through every stage, and publish courses and posts.

The app supports English, French, Japanese, and Spanish, and was designed for phones and iPad.

What made it complex

Two sides in one app: people offering skills and people booking them
A full booking lifecycle, including structured cancellations and disputes
Courses, posts and reels alongside bookings
Identity checks with face verification and date of birth
Four languages across phone and iPad

Key decisions we made

Two or three decisions and whyFor example, a rule you simplified, a feature you cut from version one, or a trade-off the client accepted.

What the product does

Every feature below was specified in the requirements and shown in the designs.

Skill listings. Add skills with a fee, description, and media.
Bookings. Pending, scheduled, completed, and cancelled bookings with full details.
Cancellations. Structured cancellation reasons for every booking.
Disputes. Dispute details and status tracking for a booking.
Courses. Create, manage, and purchase courses.
Posts and reels. Share photos and videos, tag people, and add a location.
Messaging. Chat between members, with comments on posts.
Top-rated providers. A ranked list of the best-reviewed providers.
Identity checks. Face verification and date-of-birth confirmation.
Location. Location permission and map-based requests.
Four languages. English, French, Japanese, and Spanish.
Payments. Saved payment methods for bookings and courses.

How we worked

Discovery sessions, then business, functional and technical requirements and a data model, then design and handover. Every screen traces back to a documented requirement.

The same process, as a service

What the client received

Plain names first; the short labels are what developers call each document.

BRD

Business Requirements Document

Business goals, users, scope, and success measures.

FSD

Functional Specification Document

Every feature, flow, business rule, and screen behavior.

TRD

Technical Requirements Document

Architecture, integrations, security, and performance requirements.

ERD

Entity Relationship Diagram

The data model behind the product and how its records connect.

Design

UX and UI design

185 screens, ready for development handover.

Pitch deck, if deliveredAdd as a deliverable where you prepared one for this client.

A look inside the product

8 of the 185 screens we designed. Scroll or swipe to see more.

Outcome

What happened nextOne true sentence, for example: the client selected a development partner, raised investment, or started the build. Remove this block if it cannot be shared.

185Screens designed

4Languages

Content needed: a real quote from this client, two or three sentences, in their own words

Content needed: role, company type and country (name optional)

Have a product like this in mind?

We start with discovery: requirements, documentation and design that any development team can quote and build from.

Book an intro call

Free and without obligation. Content needed: call length

Before the callWe read what you sent, so the call starts with your problem.
On the callWe ask questions, listen, and explain how we would approach it.
After the callIf we are a fit, a written proposal with a fixed scope follows. If not, we say so.