What you will learn
- All 93 verticals, from health and fintech to aerospace and AI/ML platforms
- 12 distinct project guides per vertical — 1,116 guides in total
- Core features, build phases, tech considerations, and challenges per project
- How to compare neighbouring projects before committing to a scope
How to use these guides
Start with the vertical that matches your business, then read the guide for the project closest to your idea. Each guide is written around one specific project type — a pharmacy delivery app is not a clinic management system, and a solar quoting platform is not a solar monitoring app — so the features, workflows, and risks are the ones that actually belong to that build. If two guides both look close, read both: the differences between them are usually the scope decisions that matter most in version one.
Every guide follows the same structure so you can compare fairly: what the project is, who uses it, core features, build phases, technology considerations, challenges, and frequently asked questions. Cost and time appear only as typical, approximate ranges, because a real quote depends on your exact scope — the guides say so rather than inventing a figure.
How each guide is structured
Guides lead with a direct answer to what the project is, then move into the detail a buyer or builder needs: the feature set that defines a credible version one, the phases a build usually runs through, the integrations and data questions that cause rework when missed, and the pitfalls that show up after launch rather than before it. The related guides at the bottom of each page point to the closest alternatives in the same vertical and to equivalents in other verticals, so you can check your scope against neighbouring ideas before you commit.
What comes next
This is Wave 1. The full vertical map, kept alongside this hub, lists every further vertical identified for later waves — including railways, mining, publishing, waste management, and public safety — each with a project-count estimate. Later waves follow the same rule as this one: a project only earns a guide if it can sustain one on its own specific content, and anything that cannot is merged or dropped rather than padded.
Frequently asked questions
What is a project guide?
A project guide explains one specific software project: what it is, who uses it, its core features, how it is built in phases, the technology choices involved, and the challenges to plan for. It is written to help you scope a real build, not to sell a template.
How many verticals and projects are covered?
Waves 1 and 2 cover 93 verticals with 12 project guides each — 1,116 guides in total — plus a hub page for every vertical. More verticals are mapped for later waves.
How do I choose the right project guide?
Start from the vertical hub closest to your business, then pick the guide whose user and transaction match yours. Each guide states plainly what the project fits and where its scope ends, so you can rule out near-misses fast.
Do the guides include costs or timelines?
Costs and timelines are given only as typical, approximate ranges, with a note to confirm with a written quote. No guide invents a precise price, timeline, or client result.
Can I get one of these projects built for my business?
Yes. Every guide ends with a contact block — email or WhatsApp — to start a hire enquiry for that exact project type.