What's inside the mockup: three examples for different project types
In the previous post we wrote: after a request on raisberg.ee, within 24 hours you get a mockup. The most common follow-up question: "But what exactly is a mockup?"
The answer depends on the project. A landing page and a Telegram Mini App differ in content. But the base skeleton is the same. To make it concrete - three illustrative examples based on real projects. We omit client and brand names; we describe the functionality and what was in the mockup.
What's in there in general
A mockup always includes a few things:
- What we'll build - a list of features and screens. Concrete, no "and much more".
- What it'll look like - the actual screens of your future product: what taps where, how the key flows work.
- How much it costs - a concrete price with what's included and what isn't. Starting prices are openly published on raisberg.ee.
- How long it takes - a concrete delivery date broken down by week: what you see in the demo after one week, what after two.
Now - three examples of how that looks for different project types.
Example 1: bookings for a nail technician
The request came in like this: "I do nails at home, I keep bookings in a notebook, clients keep confusing the times. I want something in Telegram so they can pick a slot themselves." We hopped on a call, talked through the problem, and the next day sent over the mockup. It showed every screen of the future app - how the client picks a service, date and time, how reminders arrive, how the technician sees and manages their bookings. Alongside it: what the work includes and what it doesn't, a concrete price, and a delivery date down to the day. The client decided in two days; on the next call we only discussed colours and the logo.
Example 2: expense tracking for a dental practice
The request: "We have a private dental practice, I work out service pricing in Excel. Each service has a pile of materials, I need to see the margin on every procedure, and Excel is starting to fall apart." This one turned out trickier than it looked. On the call we mapped out what was needed: a catalog of services and materials, the links between them, and automatic recalculation of every service's cost when a material's purchase price changes - plus a dashboard with the margin per procedure and the most and least profitable items. The next day the client got the mockup: how it would look, what goes into the first version and what doesn't (which later prevents arguments), the price and a day-by-day timeline. When, two weeks after launch, they asked to add something new - we just went back to that mockup and scoped the next iteration as a separate project.
Example 3: AI receipt processing for accounting
The request: "Our accountant spends 4 hours a day re-typing receipt data into Excel. Can we do something about that with AI?" Here the task turned out simpler than it seemed. We had a call, and the next day sent the mockup: a web service where you upload receipt photos, AI reads the sum, date, vendor and category, and the accountant checks it, fixes anything that's off, and exports a ready Excel file in one click. The mockup also had an honest-limitations section: recognition is never 100% accurate, so manual review stays mandatory - the service helps the accountant, it doesn't replace them. Plus, of course, the price and the timeline. We always add that limitations section when AI is involved - better to say it plainly up front than to sort it out a month later.
Why we make it within 24 hours
Because there's no one between your request and the person who'll actually do it. The same developer who received and worked through your request also puts the mockup together - the task doesn't get passed down a chain of account manager, project manager and team lead. So preparing a mockup like this is just part of the work for us, not a separate long and expensive stage. Why this works for two people and doesn't for a 70-person agency - we covered that in the post Who Raisberg is, and why two developers reply within 24 hours.
If you have an idea - leave a request
If you have an idea - even raw - open raisberg.ee, describe it in 3-5 sentences. No technical language needed, no spec required. Describe it the way you'd explain it to a friend over coffee.
By this time tomorrow, you'll have a mockup in your inbox similar to one of the three above. Free, no calls, no signatures.
Raisberg OÜ is a Tallinn-based agency of two developers. Landing pages, MVPs, AI automation, Telegram Mini Apps for small and medium businesses in Estonia and Europe. Open pricing from €800. Free 24-hour mockup before any contract.