Solutions
Find the closest starting point.
Start with the scale of the work, the kind of system you need, or the shape of the app. Each solution helps you choose a clearer first build without overthinking the stack.
By Size.
Pick the scale you are building for.
Personal Apps
Turn a tracker, planner, or small idea into a real app without overbuilding the stack first.
Best for: Personal tools, side projects, and focused products you want to use yourself or share with a small audience.
Businesses
Run bookings, intake, CRM, and day-to-day operations in one app shaped around how the business already works.
Best for: Service businesses, local operators, and teams moving core workflows online.
Teams
Give a larger group one shared system for workflows, visibility, and product changes that keep moving.
Best for: Organizations with many people touching the same app or process.
Startups
Ship a first product people can use while the idea is still changing, without assembling a stack first.
Best for: Founders who need a real first version before the company has an engineering department.
Agencies
Deliver client work as a living app instead of restarting the stack for every engagement.
Best for: Studios and agencies that ship client products and then need to keep changing them.
By need.
Pick the workflow you want to unlock first.
Internal Tools
Build the dashboards, approvals, and operator views teams use to run the real work.
Best for: Operators, support teams, finance, and admins who need software shaped to how the company runs.
Automation
Run recurring and event-driven work without turning automation into its own fragile side project.
Best for: Teams reducing repeat work, notifications, syncs, and background operations.
Customer Apps
Put the public or customer-facing flow in the same product as the work behind it.
Best for: Products people outside the company use: requests, accounts, self-serve flows, and follow-up.
Portals
Give customers, vendors, or partners one place to see status and take the next step.
Best for: Businesses that need a shared, login-gated space for status, files, requests, or records.
Records
Start with a table for the business, then grow small listeners and jobs around the rows.
Best for: People who think in columns first, and want that table to start doing work without designing a full interface.
First Versions
Go from an idea to a product you can put in someone's hands before the spec is finished.
Best for: Anyone who needs a first working version to learn, share, or sell the idea.
By use.
Pick the shape of app you want first.
Bookings
Coordinate time, availability, and follow-up in one booking loop.
Best for: Services, studios, clinics, tutors, and anyone who sells or assigns time.
Dashboards
Give operators live views of status, counts, and the next action.
Best for: Teams who start every day by asking what needs attention.
Intake
Collect requests, applications, or sign-ups and work them through to a result.
Best for: Teams that take submissions and then have to review, assign, or follow up.
Operations
Run jobs, inventory, field work, or other daily execution from one live state.
Best for: Operators who update status all day and need everyone looking at the same work.
Memberships
Keep members, access, and the reason people come back in one product.
Best for: Groups, programs, and products with members who return.
Catalogs
Browse items, then take the next action without leaving the listing behind.
Best for: Businesses and makers who need a living catalog with inquiry, order, or booking on the same item.
What a solution gives you.
A starting shape, not a rigid template.
A solution is a clear starting point for a certain kind of app, a certain size of team, or a familiar use. Each one shows what to model first, what screens matter early, and how to keep the first release moving.
These are not clone-and-go templates. They are the app shapes and product decisions that make a first version easier to build and easier to keep changing.
Explore will handle installable starters later. Solutions are here to help you make the first product decision without getting lost in options.
Pick the closest fit
Start with size, need, or use — whichever makes the decision clearer.
See the shape
See what to model first, what screens matter early, and how the flow grows.
Ship on App Marché
Turn the solution into a working app inside one product.
