# 22 App Ideas to Build with AI, Each with a Prompt

> App ideas you can build today, each with a starting prompt: CRMs, marketplaces, booking systems and dashboards, plus native iOS and Android apps.

Canonical: https://vibely.sh/use-cases
Last updated: 2026-10-20

Web apps and native iOS and Android apps are on every plan; App Store and Google Play publishing is on Lite, Pro and Business.

## Internal tools

### [The internal tool your team keeps asking for](https://vibely.sh/use-cases/internal-tools)

Web app

Dashboards, admin panels and workflow apps with a real database, roles and a live URL — instead of another shared spreadsheet.

### [Build a CRM shaped like your pipeline, not someone else’s](https://vibely.sh/use-cases/crm)

Web app

Most small teams do not outgrow their CRM — they outgrow the shape of it. The stages are wrong, half the fields are dead, and the part that actually matters lives in a side spreadsheet nobody else can see. A custom CRM is not a big build: it is contacts, a pipeline, activity history, and permissions. Vibely produces all four from a description, on a Postgres database via Supabase, deployed to a URL your team can open the same afternoon.

Who it is for: This is for a team of two to twenty whose pipeline does not fit the template, and whose alternative today is a shared sheet with colour-coded rows. It also suits freelancers and agencies tracking clients, who want a client management app that matches how they work. If you need forecasting rollups across regions and a marketing automation suite, buy one — the argument here is fit and ownership, not feature count.

Starting prompt:

> Build a CRM for a five-person sales team.
> 
> Screens: a pipeline board with the stages New, Qualified, Proposal, Won and Lost where I can drag a deal between columns; a contacts list with search and a filter by owner; and a contact detail page showing the company, deal value, and a timeline of notes and calls.
> 
> Data: companies, contacts, deals and notes in Supabase. Sign-in with email. A rep sees the deals they own; a manager sees everyone’s.
> 
> Start with about twenty realistic seed records so I can see it working.

### [Build the operations dashboard instead of exporting another spreadsheet](https://vibely.sh/use-cases/ops-dashboard)

Web app

The weekly numbers exist. They are just in four places, and somebody spends Monday morning turning them into a slide nobody trusts by Wednesday. A dashboard is a query, a few charts, a date filter and permissions — small enough that it never gets a roadmap slot and important enough that its absence costs a morning a week. Vibely builds it against your own Postgres database and deploys it to a URL, so the meeting looks at one live screen instead of four stale exports.

Who it is for: For an operations, finance or support lead whose data is already in a database or a CSV somebody exports on a schedule. If the data does not exist yet, build the tool that captures it first — an internal tool or a tracking app — and the dashboard follows from it.

Starting prompt:

> Build an operations dashboard for a support team, against my Supabase database.
> 
> Top of the page: four tiles — tickets opened, tickets closed, median first response time, and open tickets older than seven days.
> 
> Below that: a line chart of opened versus closed per day, and a bar chart of tickets by category.
> 
> Everything is driven by one date-range picker at the top, defaulting to the last thirty days, plus a filter by team.
> 
> Underneath, a table of the currently open tickets, sorted oldest first, that I can click into.
> 
> Sign-in with two roles: a lead sees their own team, an admin sees all teams.

### [Build a client portal your clients will actually log in to](https://vibely.sh/use-cases/client-portal)

Web app

Client work leaks across tools. The latest file is in one email, the approval is in another, and the status lives in your head until the client asks for it. A client portal fixes that with four things: a login per client, the projects that belong to them, the files and updates for each one, and a clear place to approve. Vibely builds all four from a description, on a Postgres database with authentication via Supabase, and deploys it to a URL you can send to your first client the same day.

Who it is for: This is for consultants, agencies, accountants, designers and studios with somewhere between a handful and a few hundred clients, who are tired of explaining where the latest version is. If you need contracts, e-signatures and invoicing in one suite, a dedicated product will cover more ground — the case here is a portal that matches how you deliver, under your own brand.

Starting prompt:

> Build a client portal for a small design studio.
> 
> Screens: a sign-in page; a client dashboard listing their projects with a status badge (In progress, Waiting on you, Done); a project page with a timeline of updates, a file list with upload and download, and an Approve button for the current deliverable; and an admin area where the studio sees every client and project.
> 
> Data: clients, projects, updates, files and approvals in Supabase, with files in Supabase Storage. Each client only sees their own projects. Studio staff see everything.
> 
> Add two example clients with a few projects each so I can see it working.

### [Build an inventory management app that matches your stockroom](https://vibely.sh/use-cases/inventory-management-app)

Web app

An inventory spreadsheet works until two people edit it on the same day. Then the counts drift, nobody knows which row is true, and the first sign of a problem is a customer order you cannot fill. An inventory app is a short list of parts: items, locations, a record of every movement in and out, and a warning when something runs low. Vibely builds those from a description, on a Postgres database via Supabase, so every change is a recorded movement instead of an overwritten cell.

Who it is for: This is for small shops, makers, warehouses, workshops and offices that track somewhere between a few dozen and a few thousand items. If you need deep accounting integration, barcode hardware fleets and multi-country warehousing, an established inventory platform is the safer buy — the case here is a tool that fits how you count, owned by you.

Starting prompt:

> Build an inventory management app for a small shop with two locations.
> 
> Screens: an items list with search, category filter and total stock; an item page showing stock at each location and its movement history; buttons to record Stock in, Stock out and Transfer between locations; and a Low stock page listing items below their reorder level.
> 
> Data: items, categories, locations and stock movements in Supabase. Stock levels are calculated from movements. Sign-in with email; staff can record movements, managers can edit items and reorder levels.
> 
> Add about thirty realistic items so I can see it working.

### [Build an invoice app shaped around how you bill](https://vibely.sh/use-cases/invoice-app)

Web app

Invoicing tools are built for the average business, so you end up bending your billing to fit them — or keeping invoices in a word processor and chasing payments from memory. The app underneath is small: clients, invoices with line items and tax, a status that moves from draft to sent to paid, and a list of what is overdue. Vibely builds that from a description, on a Postgres database via Supabase, and can add a Stripe pay button so clients settle an invoice online.

Who it is for: This is for freelancers, studios and small service businesses whose billing does not fit a template — retainers, milestones, unusual tax lines, or invoices in more than one currency. If you need full double-entry bookkeeping and tax filing, use accounting software; the case here is an invoicing tool that matches how you work.

Starting prompt:

> Build an invoicing app for a freelance designer.
> 
> Screens: a clients list; an invoice editor with line items (description, quantity, rate), a tax rate and automatic totals; an invoices list with status Draft, Sent, Paid or Overdue; a dashboard showing total unpaid and a list of overdue invoices; and a clean printable invoice page with my logo.
> 
> Data: clients, invoices and line items in Supabase. Invoice numbers increase automatically. Sign-in with email.
> 
> Add a few example clients and invoices so I can see it working.

## Products to sell

### [A SaaS MVP people can sign up for](https://vibely.sh/use-cases/saas-mvp)

Web app

Accounts, a Postgres database and a live URL, so the first version is in front of real users in days rather than a quarter.

### [Build a marketplace where both sides can actually transact](https://vibely.sh/use-cases/marketplace)

Web app

A marketplace is the hardest MVP to fake, because nothing is testable until both sides work: someone has to be able to list a thing, and someone else has to be able to find it and pay for it. That is five screens, a schema with real relations, file uploads and a payment flow — the reason most marketplace ideas die as a landing page with a waitlist. Vibely builds the whole loop from a description, so the first thing you test is the transaction rather than the pitch.

Who it is for: For a founder testing whether supply and demand will actually meet, and for an operator formalising a marketplace that currently runs on a WhatsApp group or a Google Form. It is a first version to put in front of real users, not a regulated payments platform — read the payments answer below before you assume otherwise.

Starting prompt:

> Build a marketplace for people renting out camera gear locally.
> 
> Seller side: a form to post a listing with photos, a daily price, a description and a category, plus a page showing my listings with edit and delete.
> 
> Buyer side: a browse page with search, a category filter and a price sort; a listing detail page with a photo gallery, the owner’s profile and a Book button.
> 
> Data: users, listings, categories and bookings in Supabase, photos in Supabase Storage. A seller can only edit their own listings.
> 
> Seed it with about fifteen listings across three categories so the browse page looks real.

### [Build a booking system that fits your availability rules](https://vibely.sh/use-cases/booking-system)

Web app

Off-the-shelf scheduling breaks on the rule that makes your business yours: the two-hour buffer, the room that can take six people but only four on Saturdays, the deposit before a slot is held. So the booking runs by message, and somebody keeps the real calendar in their head. A booking system is availability rules, a customer-facing flow, a confirmation and an owner view — Vibely builds those from a description, on a real database, deployed to a URL you can put on your own domain.

Who it is for: For studios, clinics, tutors, classes, rentals and service businesses whose scheduling has one rule the tools do not support. If a generic scheduling link genuinely fits your business, use one — this is for the case where it does not.

Starting prompt:

> Build a booking system for a two-room pottery studio.
> 
> Customer side: pick a class, see the open slots for the next four weeks, and book with a name, email and phone. Only show slots that are genuinely free.
> 
> Rules: classes run Tuesday to Saturday, 10:00 to 18:00, in two-hour slots with a thirty-minute buffer between them. Each room takes six people. No bookings on Sundays or Mondays.
> 
> Owner side: a sign-in, a day view and a week view of who is booked, and a way to block out a date.
> 
> Data in Supabase. Seed a couple of weeks of bookings so both views look real.

### [Build a membership site with paid plans and members-only content](https://vibely.sh/use-cases/membership-site)

Web app

Membership platforms take a cut of every subscription and decide how your site looks and what your members can do. The thing underneath is not complicated: a sign-up, a payment that unlocks access, pages only members can see, and somewhere for you to publish. Vibely builds that from a description, with authentication on Supabase and subscriptions through the Stripe connector, so your members pay you directly and the site is yours.

Who it is for: This is for coaches, creators, educators and communities who want a paid area with their own branding and rules. If you want a ready-made marketplace that brings you an audience, a large platform may still be worth its fee — the case here is owning the site and the relationship with your members.

Starting prompt:

> Build a paid membership site for a cooking course.
> 
> Screens: a public landing page with two plans (Monthly and Yearly); sign-up and sign-in; a members area with a library of lessons, each with a video link and written steps; a lesson page; an account page showing the current plan; and an admin area where I can add lessons and choose which plan can see each one.
> 
> Data: members, plans, lessons and subscriptions in Supabase. Use Stripe for the subscriptions, and only show lessons to members whose plan includes them.
> 
> Add six example lessons so I can see it working.

### [Build a job board for your niche](https://vibely.sh/use-cases/job-board)

Web app

General job sites are crowded, and niche communities — a city, an industry, a tool, a language — keep asking for somewhere that only lists the jobs that matter to them. A job board is a well-understood shape: listings, search and filters, a page per company, a way for employers to post, and optionally a fee per post. Vibely builds it from a description, on Supabase for data and accounts and the Stripe connector for paid listings.

Who it is for: This is for community owners, newsletter writers, recruiters and industry groups who already have an audience and want to give it a jobs page, or turn it into revenue. If you need an applicant tracking system with interview scheduling and offer letters, that is a different product; the case here is a focused board you own.

Starting prompt:

> Build a job board for remote design jobs.
> 
> Screens: a listings page with search and filters for job type (Full-time, Contract), seniority and timezone; a job page with the description, salary range and an Apply button that opens the employer’s link; a company page listing its open jobs; an employer sign-up and Post a job form; and an admin page to approve or reject new posts.
> 
> Data: companies, jobs and employers in Supabase. New posts wait for approval and expire after 30 days.
> 
> Add fifteen realistic listings so I can see it working.

### [Build a waitlist landing page that collects real sign-ups](https://vibely.sh/use-cases/waitlist-page)

Web app

Before you build the product, you need proof people want it — and a list of who to tell when it is ready. A waitlist page does both: a clear headline, a form, a thank-you with a place in line, and a list you own. Vibely builds it from a description and saves every sign-up to a Postgres database on Supabase, so the list is yours from the first email address, not locked inside a form tool.

Who it is for: This is for founders and makers validating an idea or warming up a launch. If you only need a single form with no logic, a form tool is fine; the case here is a page that looks like your product, with referrals and an export, that can grow into the product itself.

Starting prompt:

> Build a waitlist landing page for a meal planning app called Prepd.
> 
> Screens: a landing page with a headline, a short paragraph on the problem, three benefits with icons, and an email sign-up form; a thank-you screen that shows the person their position in line and a personal referral link; and a password-protected admin page listing sign-ups with a CSV export.
> 
> Data: sign-ups in Supabase with email, position, referral code and referred-by. Each successful referral moves the referrer up three places.
> 
> Make it clean and modern, with a warm colour palette.

### [Build a property listings site with search that actually filters](https://vibely.sh/use-cases/real-estate-listings)

Web app

An agency’s website is judged on one thing: whether the search works. Price, bedrooms, area and type have to filter instantly, the result has to be shareable as a link, and every property needs its photos, details and a way to ask for a viewing. That is listings, filters, a gallery and a request form on a real database — which is what Vibely builds from a description, with an admin screen so the agents add properties without touching code.

Who it is for: For small and boutique agencies, letting agents and developers marketing one scheme, whose current site is a brochure with a contact form. If you need to syndicate to the big property portals or sync with an agency CRM, those are integrations you would add in code against their APIs — Vibely has no property-portal connector, and we would rather say so.

Starting prompt:

> Build a website for a boutique estate agency called Harbour & Vale.
> 
> Screens: a home page with a search bar and six featured properties; a listings page with filters for price range, bedrooms, property type and area that update the URL; a property page with a photo gallery, price, bedrooms, bathrooms, a description, a simple mortgage calculator and a "Request a viewing" form; and a saved-homes page for signed-in visitors.
> 
> Admin: agents sign in to add or edit a property, upload photos, and mark it For sale, Under offer or Sold. They see all viewing requests with a status of New, Contacted or Booked.
> 
> Data: properties, photos, saved homes and viewing requests in Supabase, photos in storage.
> 
> Seed it with twelve realistic properties across three areas.

## Operations on a phone

### [Build the delivery app your drivers use, on their own phones](https://vibely.sh/use-cases/delivery-driver-app)

Native mobile app

Delivery days run on a printed manifest and a group chat full of photos nobody can search. The software that fixes it is per-driver, per-month, and still does not match your run sheet. What you need is small and specific: today’s stops in order, a map, a tap to mark delivered, a photo as proof, and the office seeing it happen. That needs a native app — location and camera on a phone in a van — and Vibely builds native.

Who it is for: For a small fleet, a distributor, a florist, a bakery or anyone whose drivers currently work from paper and a chat thread. It is not a routing optimiser or a dispatch platform; it is the app that replaces the manifest and the photo thread.

Starting prompt:

> Build a native mobile app for delivery drivers.
> 
> Home: today’s stops in sequence — address, customer name, a note, and a status chip. A progress bar at the top showing how many of the stops are done.
> 
> Stop detail: the full address, a Navigate button that opens the phone’s maps app, a phone number that dials, and three buttons — Delivered, Failed, Rescheduled. Failed asks for a reason.
> 
> Delivered opens the camera, takes a proof-of-delivery photo, records where and when, and uploads it.
> 
> A second tab with a map of today’s stops, coloured by status.
> 
> Data in Supabase: drivers, stops, statuses and photos. A driver only sees their own run.
> 
> Seed a run of eight stops so I can walk through it.

### [Build the inspection app that replaces the clipboard](https://vibely.sh/use-cases/field-inspection-app)

Native mobile app

The inspection already happens — on a clipboard, photographed at the end of the day, filed as a PDF nobody can search. The failure is not the checklist, it is that the evidence and the record never meet. An inspection app is a form, a camera, a location stamp and a signature, and it has to be native because all four of those live on the phone. Vibely builds it in React Native and Expo, against your own database, so the record is searchable the moment the inspector taps submit.

Who it is for: For property, construction, facilities, safety, plant maintenance and anyone else whose quality process is a laminated form. It suits a team that already knows its checklist — the value is capture and retrieval, not designing the inspection for you.

Starting prompt:

> Build a native mobile app for site inspections.
> 
> Home: my assigned sites, and a button to start a new inspection.
> 
> Inspection: a checklist in three sections — Exterior, Safety, Equipment — each item marked Pass, Fail or N/A. A Fail requires a note and at least one photo taken with the camera. Capture the location and time when the inspection starts.
> 
> Finish: a summary of the failures, a signature pad, and Submit.
> 
> History: past inspections for a site, newest first, with the failure count, opening into the full report with its photos.
> 
> Data in Supabase: sites, inspections, items and photos. An inspector sees only their assigned sites.
> 
> Seed three sites and a few completed inspections.

### [Build the check-in app your members open at the door](https://vibely.sh/use-cases/gym-check-in-app)

Native mobile app

Gym software is priced per member and still cannot express your class rules, your class pack, or the way Saturday works. Meanwhile check-in is a laminated sheet and attendance is a guess. What a studio needs is a member app that books a class and checks in, and a front-desk view that shows who is in the room — which has to be a real app, because a member is not going to bookmark a web page and open it at the door every morning.

Who it is for: For independent gyms, studios, climbing walls and clubs with a few hundred members and a process that does not fit the per-seat platforms. If you are running thousands of members with payroll and franchise reporting, that is a different purchase.

Starting prompt:

> Build a native mobile app for a climbing gym.
> 
> Member side: a weekly class schedule with spaces left, a tap to book, and My Classes with upcoming and past. A Check In button that is only active within thirty minutes of a class I have booked. An attendance screen showing how many sessions I did this month.
> 
> Staff side, behind a sign-in with a staff role: the next class, who is booked, who has checked in, and a manual check-in.
> 
> Rules: classes have a capacity, booking is blocked when full, and cancelling within two hours is not allowed.
> 
> Data in Supabase: members, classes, bookings and check-ins.
> 
> Send a push reminder an hour before a booked class. Seed two weeks of classes and a few members.

## Consumer apps

### [Build a habit tracker that runs on your phone, natively](https://vibely.sh/use-cases/habit-tracker-app)

Native mobile app

Every habit tracker on the store is somebody else’s theory of habits — their streak rules, their categories, their idea of what counts. The one you would actually use is small: a list of habits, a tap to mark today, a streak, and a reminder at the right hour. Vibely builds that as a genuinely native React Native and Expo app, with local storage so it works offline and expo-notifications for the reminder — and you run it on your own phone through Expo Go while it is being built.

Who it is for: For anyone who has abandoned three habit apps over one missing rule, and for a first native app that is small enough to finish and personal enough to keep opening. It is also the cleanest way to see what native output actually means before you build something bigger.

Starting prompt:

> Build a habit tracker as a native mobile app.
> 
> Today screen: every habit as a row with its name, its current streak and a big tap target to mark it done for today. Done habits move to the bottom and dim.
> 
> Habit detail: a calendar heatmap of the last three months, the current and longest streak, and edit and archive.
> 
> Add a habit with a name, an emoji, and a target of daily or a number of times a week.
> 
> Settings: a daily reminder time that schedules a local notification.
> 
> Store habits and check-ins on the device so it works offline. Seed three habits with a couple of weeks of history so the heatmap has something in it.

### [Build the companion app for your conference or festival](https://vibely.sh/use-cases/event-companion-app)

Native mobile app

Event apps are quoted per event and arrive as a rebranded shell two weeks before the doors open. Meanwhile the schedule is a PDF that everyone screenshots, and a room change reaches attendees through a sign taped to a door. The app you need is the schedule, a way to save what you are attending, a map, and one channel that can interrupt a thousand people at once — which is a push notification, which means it has to be a real app.

Who it is for: For conference organisers, festivals, meetups and internal company events who want their own app for the price of building it once. If the event is a single-track afternoon, a web page is enough — this pays off when the schedule has parallel tracks and can change.

Starting prompt:

> Build a native mobile app for a two-day conference.
> 
> Schedule: sessions grouped by day, with a track filter and the time and room on each row. Tapping through shows the description, the speaker with a photo and bio, and a Save to my agenda button.
> 
> My agenda: everything I saved, in time order, with a warning when two sessions clash.
> 
> Speakers: a browsable list with profiles.
> 
> Info: a venue map image, wifi details, and the code of conduct.
> 
> Push an announcement to everyone when an organiser posts one — for example a room change.
> 
> Data in Supabase: sessions, speakers, tracks and announcements. My saved agenda lives on the device so it works without wifi at the venue.
> 
> Seed two days of sessions across three tracks.

### [Build a reminder app that notifies the way you need it to](https://vibely.sh/use-cases/reminder-app)

Native mobile app

Reminders are the one thing a web app structurally cannot do: a notification has to arrive on a locked phone, and a browser tab cannot deliver that. So every "every third day at 8pm, and again in twenty minutes if I do not confirm" rule ends up as a calendar entry that does not work like that. A native app can, and Vibely builds native — expo-notifications, real local scheduling, on a React Native app on your own phone.

Who it is for: For anyone whose reminder rule is slightly unusual — medication with a confirm, plant watering by species, recurring admin, a supplement schedule. This is also the clearest demonstration of why native matters, which makes it a good first build.

Starting prompt:

> Build a native mobile app for medication reminders.
> 
> Home: today’s doses in time order, each with the medication name, the dose, the time, and a Taken button. Anything overdue is highlighted.
> 
> Add a medication: name, dose, and a schedule — daily, specific weekdays, or every N days — with one or more times a day.
> 
> Notifications: schedule a local notification for each dose. Tapping it opens the app on today. If a dose is not confirmed within thirty minutes, notify once more.
> 
> History: a calendar view of confirmed and missed doses for the last month.
> 
> Store everything on the device so it works offline, and keep the reminders scheduled after a restart.
> 
> Seed two medications with a week of history.

### [Build a link-in-bio page you actually own](https://vibely.sh/use-cases/link-in-bio)

Web app

A link-in-bio page is the most visited page a creator has, and it usually lives on someone else’s platform: their branding, their limits on themes, and their copy of your subscriber list. The page itself is small — a photo, a stack of links, one featured thing, a sign-up form. Vibely builds all of it from a description, with an editor so you can reorder links yourself and the sign-ups going into a database you control, on a URL you can share the same day.

Who it is for: For creators, small shops and anyone whose bio link is doing real work — sending people to a newsletter, a product or this week’s video. If you only ever need three static links, a hosted link page is fine. The case for building one is owning the list, the look and the analytics, and being able to add the odd thing a template will not let you.

Starting prompt:

> Build a link-in-bio page for a ceramics studio called Kiln & Co.
> 
> Public page: a round profile photo, the name, a one-line bio, a featured card at the top (image, title and a button), then a list of links as full-width buttons, and a newsletter sign-up form at the bottom with email validation and a thank-you message. Mobile-first, warm off-white background.
> 
> Editor: a page only I can open after signing in, where I can add, edit, hide and drag to reorder links, and change the featured card.
> 
> Data: links, the featured card and subscribers in Supabase. Subscribers have email and signed-up date, and the editor can export them as CSV.
> 
> Seed it with six links and a featured card for a spring pottery class.

### [A free wedding website builder, with an RSVP that knows who is coming](https://vibely.sh/use-cases/wedding-website)

Web app

Vibely is a free wedding website builder: describe your day and it builds your story, schedule, travel notes and registry, published on a free vibelyagent.com address. The RSVP is where template sites fall short, handing you free-text replies. From Lite, Vibely makes it real data: a code per household, a meal choice per guest, and a page where you two see the totals.

Who it is for: For couples, and for the friend who has been volunteered to make the site. It is also a good first build if you have never made an app, because the shape is familiar. If all you need is a date and an address, a free page builder is enough; the case here is the RSVP and the guest list behind it.

Starting prompt:

> Build a wedding website for Priya and Sam, getting married on 14 June at a vineyard.
> 
> Pages: a home page with our names, the date, a live countdown and a photo; Our story as a timeline of five moments; The weekend with the schedule for Friday drinks, the Saturday ceremony and Sunday brunch; Travel with hotels and directions; Registry with three links; and a FAQ.
> 
> RSVP: guests enter a household code, then for each guest in the household choose attending or not, a meal (beef, fish or vegetarian) and dietary notes. Some households are allowed a plus-one.
> 
> Data: households, guests and responses in Supabase. A private page for the two of us after signing in shows totals by meal, who has not replied and a CSV export.
> 
> Seed it with twenty households.

### [Build a portfolio website with AI, free to start](https://vibely.sh/use-cases/portfolio-website)

Web app

Vibely is an AI portfolio website builder: describe your work and it builds a home page of selected projects, a page for each case study, an about page and a contact form, published free on a vibelyagent.com address. It is React and TypeScript you own, so the layout is yours rather than a theme’s, and you can download the code on Lite, Pro and Business.

Who it is for: For designers, developers, photographers, artists and students who want a portfolio that looks like their work rather than someone else’s theme. If a few images on a hosted page are enough, a portfolio service will do. The case for building one is owning the layout and the code, and adding the thing a template will not let you, like your own case-study format.

Starting prompt:

> Build a portfolio website for Maya Chen, a product designer.
> 
> Pages: a home page with my name, one line about what I do and a grid of six selected projects; a page for each project with the brief, my process in three steps, the screens and the result; an About page with a short bio and my experience; and a Contact page with a form for name, email and message.
> 
> Style: clean and editorial, plenty of white space, one accent colour, mobile-first.
> 
> Seed it with six projects.

## Related

- [Features](https://vibely.sh/features)
- [Pricing](https://vibely.sh/pricing)
- [App templates](https://vibely.sh/templates)
