MAXIMUM Work Samples
MAXIMUM. RU Send a brief

Work samples · 2026

Product engineering for startups and design agencies

MVPs, web apps, storefronts and AI assistants, built from your Figma files or a product brief. Under your brand or ours.

  • Fixed-price paid pilot
  • demo build every week
  • code and IP are yours
  • calls on US mornings

Concept projects

Four working demos

MAXIMUM launched in 2026. Until our first client case studies go public, these concept projects for fictional brands show the level of work. Each one is live: open it and click through.

Product configurator · Concept project

Kerf

A cabinetry website where the quote request arrives already drawn and priced.

Custom-kitchen shops usually ask for a phone number and quote after a home visit. This site gives the customer a price range and a drawing of their walls in six steps, and hands the shop a complete spec.

Kerf estimate screen: an L-shaped kitchen elevation with dimensions in inches beside a six-step quiz
  • 7,488layout and material combinations, each drawn and priced, before wall sizes
  • 6 stepsfrom kitchen shape to a request the shop can quote from
  • 19 KBthe whole page over the network, gzipped, fonts aside
  • 0JavaScript libraries or frameworks

The problem

Customers rarely book a home visit before they see a ballpark price. The shop calls back knowing only a name, and gallery photos never match the customer’s room.

Kerf is fictional, so we set the brief ourselves from how cabinet shops sell today.

  • Six-step quiz

    Shape, wall lengths, doors, countertop, uppers and extras, then contact details. Price and lead time change on every answer.

  • Live wall elevation

    An SVG drawing redraws to the customer’s walls, dimensioned in inches, with a title block like a shop drawing.

  • Request as a ready message

    The estimate leaves by text or email with layout, sizes, materials and budget filled in.

  • Projects that recalculate

    Six gallery kitchens, filtered by layout. Any of them opens in the calculator and adapts to the customer’s walls.

How the price is calculatedfeet · US dollars
cabinets   = wall length × door rate × uppers factor
countertop = (wall length − 2 ft if pantry) × top rate
corners    = $600 for each corner
island     = length × (door rate × 0.68 + top rate) + $500
extras     = pantry, drawers +12%, light $40/ft, install $350
estimate   = total −7% … +10%, rounded to $100

Doors, per foot

Matte laminate
$520
High-gloss acrylic
$680
Painted MDF
$900
White oak veneer
$1,250

Uppers and top

Open shelves
× 0.72
30″ wall cabinets
× 1.00
To the ceiling
× 1.22
Quartz top, per foot
+$175

Default kitchen: L-shape, 126″ + 72″, painted MDF, quartz, lighting and installation. Estimate $18,000–$21,300.

For a real shop we would add

  • Rates the shop edits itself in an admin panel or a shared spreadsheet.
  • Requests in the CRM with the drawing and spec attached.
  • Drop-off by quiz step in analytics.
  • Real photos of each kitchen next to its drawing.

E-commerce · Concept project

Forage

A tea store where the packaging identity carries all the way through checkout.

Small food brands invest in packaging, then sell it through a generic store theme. We built the catalog, cart and checkout around the brand’s own tins, colors and illustrations.

Forage herbal tea store catalog with colored tin cards and purpose filters
  • 8 teaseach in a 2 oz and a 4 oz tin, with filters by purpose and price sorting
  • $50free-shipping threshold, tracked live in the cart
  • 3 + 3delivery and payment options at checkout
  • 14 KBthe whole page over the network, gzipped, fonts aside

The problem

A strong tin on the shelf turns into a plain product grid online. Customers can’t tell the blends apart, and the cart gives no reason to add one more.

Forage is fictional, so we set the brief ourselves.

  • Catalog with filters and search

    Filter by purpose, sort by price and pick the tin size right on the card.

  • Quick view

    Ingredients, water temperature and steep time open without leaving the page.

  • Cart with promo codes

    The free-shipping bar and discounts update as the cart changes. Try the code FIRST10.

  • Checkout and confirmation

    Delivery, payment and contact details on one screen, then an order confirmation.

How the cart total is calculatedUS dollars
items     = Σ tin price × quantity
discount  = FIRST10 −10% · TRIO −15%
after     = items − discount
shipping  = $0 if after ≥ $50, otherwise by method
total     = after + shipping

Delivery

USPS Ground, 3–5 days
$6
Local, Portland, next day
$9
UPS 2nd Day Air
$14

Payment

Apple Pay or Google Pay
one tap
Card
Visa · MC · Amex
PayPal
log in

For a real store we would add

  • Checkout on Shopify or Stripe, with the same design.
  • Stock and prices from the store admin.
  • Order and shipping emails in the brand’s style.
  • Live carrier rates instead of fixed prices.

SaaS dashboard · Concept project

Tempo

A studio back office where the owner, the front desk and instructors each see what they need.

Yoga and dance studios often run on spreadsheets and group chats. We designed and built the core of a SaaS product for them: revenue, clients, staff roles and subscription billing.

Tempo dashboard with revenue and visits chart, attention list and room occupancy
  • 4 periodsweek, month, quarter and year; every chart and metric recalculates
  • 36 clientssample base with search, four pass statuses and profiles
  • 3 rolesowner, front desk and instructor across seven permissions
  • 15 KBthe whole app over the network, gzipped, fonts aside

The problem

The owner can’t see revenue by period without a spreadsheet, expiring passes go unnoticed, and every staff member sees the same data whether they need it or not.

Tempo is fictional, so we set the brief ourselves.

  • Dashboard with periods

    Revenue, passes, visits and churn for the week, month, quarter and year, with a list of what needs attention.

  • Client base

    Search, status filters and a client profile with visit history and one-click renewal.

  • Roles and permissions

    Each role gets its own view. Staff are invited by email.

  • Plans and limits

    Monthly and yearly billing, usage meters and invoice history.

What each role can see3 roles · 7 permissions
PermissionOwnerFront deskInstructor
Schedule and bookings
Own classes and attendance
Client profiles and contacts
Selling and renewing passes
Revenue and analytics
Staff and permissions
Plan and billing

For a real product we would add

  • Recurring payments on Stripe Billing.
  • Bookings backend with class reminders.
  • Staff sign-in and email invites.
  • CSV export of clients and revenue.

AI assistant · Concept project

Furrow

A support assistant that answers only from the knowledge base and hands off when it isn’t sure.

A grocery delivery service gets the same questions every day, and a generic chatbot can invent a refund policy. This assistant cites the article behind every answer, checks orders by number and passes the rest to a person.

Furrow support chat beside a trace of how the assistant found its answer
  • 12 articlesin the knowledge base, the only source the assistant answers from
  • 60%confidence threshold; below it a person takes over
  • 7 questionsready to try in one tap, from order status to a wholesale request
  • 10 KBthe whole page over the network, gzipped, fonts aside

The problem

Most support questions repeat: delivery zones, fees, refunds, order status. A bot that guesses creates more tickets than it closes, and the team can’t see why it answered what it did.

Furrow is fictional, so we set the brief ourselves.

  • Grounded answers

    Every reply comes from an article the team wrote and shows that article as its source.

  • Order lookup

    An order number in the question triggers a status check before anything else.

  • Human handoff

    Low confidence or a staff-only topic opens a ticket with the full chat history.

  • Answer trace

    A side panel shows each step, the matched words and the confidence, so the team can fill gaps.

How an answer is chosenin the demo browser
  1. Read the questionDrop filler words, reduce words to stems, look for a five-digit order number.
  2. Check the orderWith a number, reply from the order status first.
  3. Score every articleRare words weigh more, title matches count 1.4×, confidence comes from coverage and score.
  4. 60% or higher: answerReply with the article text and show it as the source.
  5. Below 60% or a staff topic: hand offOpen a ticket with the chat history and tell the customer someone will reply.

The demo matches articles in the browser so it runs without an API key. In production a language model writes the reply from the same articles.

For a real service we would add

  • A language model answering from the same articles, with the source cited.
  • Order status from the store’s API.
  • Tickets in the help desk the team already uses.
  • A test set of real questions checked before every change.

Two ways to work with us

For founders and for agencies

Startups

Your MVP or the next piece of your product

  • Start with a paid pilot: one feature, screen or audit in 1–2 weeks at a fixed price.
  • Then two-week sprints with a working demo build every week.
  • The repository is yours from day one. IP is assigned to you on payment.
  • AI features done properly: grounded answers, evaluations, human handoff.

Design and marketing agencies

Your designs, built under your brand

  • Figma to Webflow, Framer, Shopify or Next.js, pixel for pixel.
  • White-label: your client only ever sees your agency.
  • NDA and a no-poaching clause in every contract.
  • A milestone quote before any work starts. No retainer required.

Rather hand off the whole client? We pay 20% of every payment that client makes for 12 months.

Process

How a project runs

  1. 30 minutesIntro callYour goals, deadline, budget range and what already exists.
  2. after the callScoped proposalMilestones, a fixed price per milestone and what you get at each one.
  3. 1–2 weeksPaid pilotOne real piece of the product, so you can judge the work before committing.
  4. 2-week sprintsBuildWeekly demo builds, a shared tracker and a written update every Friday.
  5. launchHandoverCode, documentation, accounts and access, transferred to you.

Stack

What we build with

  • Next.js
  • React
  • TypeScript
  • Node.js
  • Python
  • PostgreSQL
  • Stripe
  • Shopify
  • Webflow
  • Framer
  • OpenAI and Anthropic APIs
  • Vercel
  • AWS
  • Google Cloud

Contact

Send a Figma link or a short brief

We’ll come back with questions or a scoped estimate. Or book a 30-minute call.

FounderMaxim Prokopyev
Emailmaksim.prokopiew@gmail.com
Websitemaximumstudio.dev ↗