What if your next side project solved a real problem—not just another CRUD tutorial?
The UN's 17 Sustainable Development Goals (SDGs) offer a useful map of problems worth exploring. They are not a list of guaranteed startup opportunities, and software alone cannot solve structural problems. But they can help us ask better product questions.
Imagine a bakery throwing away edible food while people nearby struggle with grocery costs. A rural school has tablets but no reliable internet. A small clinic loses hours to paperwork. A city owns buses but lacks trustworthy operational data.
These are not necessarily AI problems. They are coordination, access, information, logistics, and workflow problems. Sometimes a modest web app is more useful than an impressive model.
This article explores three buildable software ideas for each of the 17 SDGs—51 ideas in total—and connects them to documented examples. For every goal, we'll look at a possible MVP, the customer or partner, and a meaningful impact metric.
A note on evidence: The real-world examples below are inspiration and proof that an approach has been attempted, not validation of the proposed startup ideas. Where I mention a product, it does not mean its business model is profitable or transferable to your market. Sources are linked throughout; the central UN/ITU collection contains 34 documented digital solutions across all 17 SDGs (SDG Digital showcase).
A quick product lens: impact ≠ adoption ≠ revenue
Before building anything, ask three separate questions:
- Impact: What measurable outcome improves for whom?
- Adoption: Who experiences the pain frequently enough to change their workflow?
- Sustainability: Who pays—or funds and maintains—the service over time?
A dashboard that measures a problem is not the same as a system that changes the outcome. And a social benefit does not automatically create a viable subscription business.
SDG 1 — No Poverty: make support easier to reach
Poverty is not just missing money; people can also miss benefits, services, and opportunities because the system is difficult to navigate.
Three software ideas
- Benefits navigator: a privacy-conscious eligibility checker that explains public assistance programs in plain language and links to official applications.
- Income-stability planner: a lightweight cash-flow and payment-reminder tool for irregular-income workers, designed to work on low-end phones.
- Community referral network: a case-management platform helping local nonprofits refer people to food, housing, employment, and legal support without duplicating intake.
MVP to try: choose one city and five benefits; build a searchable eligibility guide with human-reviewed rules, source dates, and an explicit warning that results are indicative.
Who might sustain it? Municipalities, nonprofits, foundations, or employers—not necessarily the people in need.
Measure: successful referrals, completed applications, and time saved—not app downloads.
Reality check: Eligibility rules change, and incorrect advice can cause harm. Avoid automatically deciding who deserves assistance.
Research trail: UNDP: Digital Public Goods for the SDGs examines replicability, governance, and sustainability of public-interest digital systems.
SDG 2 — Zero Hunger: improve food access and reduce loss
A surprising amount of the food problem is about timing, coordination, and supply-chain visibility.
Three software ideas
- Surplus-food exchange: connect bakeries, groceries, and restaurants with customers or food-rescue organizations before food expires.
- Small-farm demand planner: aggregate buyer demand so growers can plan harvests and deliveries more accurately.
- Food-bank inventory router: track stock, expiry dates, dietary requirements, and delivery priorities across distribution sites.
MVP to try: one neighborhood, ten food businesses, a simple listing/reservation flow, and pickup windows. Start with manual onboarding rather than sophisticated optimization.
Who might sustain it? Merchants through commissions or subscriptions; foundations or public programs for donation logistics.
Measure: kilograms of edible food redistributed, successful pickups, and spoilage reduction.
Case study — Too Good To Go: The platform connects consumers with businesses selling surplus food at reduced prices. Peer-reviewed studies examine its combination of commercial value and environmental impact. Its success depends on both sides of the marketplace participating—not just on the app itself (2021 research; 2023 case study).
Reality check: Food safety, pickup reliability, and local density are harder than the CRUD implementation.
SDG 3 — Good Health and Well-Being: remove administrative friction
Not every health-tech product needs to diagnose disease. Better coordination and follow-up can matter enormously.
Three software ideas
- Small-clinic operations SaaS: appointments, patient records, follow-up reminders, and billing for under-digitized practices.
- Medication adherence companion: opt-in reminders and caregiver alerts, without making medical recommendations.
- Community-health referral tracker: help authorized professionals coordinate appointments and follow-up across organizations.
MVP to try: one practice, scheduling plus secure reminders, with clear permissions and audit logs.
Who might sustain it? Clinics, health networks, and public-health organizations.
Measure: missed appointments, administrative hours, and completed follow-ups.
Research trail: UNDP's digital public goods case studies illustrate why governance and institutional adoption matter as much as code.
Reality check: Health information is sensitive. Consent, access control, security, local law, and clinical oversight are non-negotiable. A veterinary clinic system can improve animal care, but it should not be casually described as achieving human-health SDG 3.
SDG 4 — Quality Education: design for the learner's real environment
A beautiful learning app that requires fast internet may exclude the students who need it most.
Three software ideas
- Offline-first learning library: downloadable lessons, quizzes, and teacher progress sync when connectivity returns.
- Adaptive practice engine: diagnose gaps in mathematics or reading and recommend targeted exercises with teacher oversight.
- Teacher workflow assistant: lesson planning, assignment distribution, and feedback without requiring students to have personal accounts.
MVP to try: one subject, one grade, offline exercises, and a teacher dashboard. Test on inexpensive Android devices.
Who might sustain it? Schools, education networks, foundations, or government programs.
Measure: learning gains, lesson completion, and usage under poor connectivity—not time spent in the app.
Case study — Kolibri: Learning Equality's Kolibri is designed for teaching and learning where internet access is limited. It demonstrates that offline-first is a product requirement, not merely an engineering optimization.
Reality check: Curriculum alignment, teacher training, and evidence of learning outcomes are the difficult parts.
SDG 5 — Gender Equality: reduce barriers without collecting unnecessary data
Software can help expose inequities and improve access, but it cannot substitute for institutional change.
Three software ideas
- Pay-transparency analyzer: help organizations audit compensation patterns and explain disparities responsibly.
- Return-to-work network: match caregivers re-entering the workforce with training, mentors, and flexible opportunities.
- Safe-reporting workflow: confidential reporting and case tracking for organizations with independent, trained responders.
MVP to try: an anonymized pay-band reporting tool for one industry, with minimum group-size thresholds.
Who might sustain it? Employers, industry associations, and nonprofits.
Measure: corrected pay gaps, successful placements, or time to resolve cases—subject to rigorous privacy safeguards.
Research trail: The ITU/UNDP SDG Digital showcase includes digital approaches to women's empowerment.
Reality check: Do not build a reporting tool without a credible response process. Privacy failures can put people at risk.
SDG 6 — Clean Water and Sanitation: make invisible losses visible
Water infrastructure often fails quietly: a leak can continue for weeks before anyone notices.
Three software ideas
- Leak-detection analytics: flag unusual meter patterns in buildings and commercial properties.
- Community water-quality log: let trained operators record sampling results, location, and maintenance actions.
- Sanitation maintenance scheduler: prioritize inspections and repairs for facilities with limited maintenance budgets.
MVP to try: ingest daily meter readings from CSV; detect abnormal consumption using simple baselines; send reviewable alerts.
Who might sustain it? Property managers, utilities, and municipalities.
Measure: verified leaks detected, water saved, and repair response time.
Research trail: The GSMA SDG reports document mobile-enabled utility and infrastructure partnerships; the broader SDG Digital showcase catalogs goal-specific solutions.
Reality check: Meter data quality, hardware access, and false positives may dominate the engineering effort.
SDG 7 — Affordable and Clean Energy: optimize what already exists
For many customers, the immediate value proposition is lower energy bills and fewer outages.
Three software ideas
- Energy anomaly detector: identify unusual consumption and likely equipment issues from smart-meter data.
- Solar return-on-investment planner: model solar installations using local tariffs, shading assumptions, and consumption patterns.
- Community microgrid dashboard: visualize generation, storage, demand, and maintenance for local operators.
MVP to try: utility-bill upload plus monthly usage analysis and transparent savings scenarios.
Who might sustain it? Building managers, installers, energy service companies, and utilities.
Measure: verified kWh reduction, reduced outage duration, and payback accuracy.
Case study — smart metering: GSMA describes a collaboration involving Jazz, CISNR, and PESCO in Pakistan to explore mobile-enabled detection of electricity theft and distribution losses (GSMA case study). It is a reminder that operational data becomes valuable when utilities can act on it.
Reality check: A savings estimate is not verified savings. Show assumptions and uncertainty.
SDG 8 — Decent Work and Economic Growth: build for overlooked businesses
Millions of small businesses need fewer spreadsheets and less repetitive administration—not a full enterprise ERP.
Three software ideas
- Microbusiness operations SaaS: inventory, sales, invoicing, and basic reporting with a minimal learning curve.
- Shift and labor-compliance planner: scheduling, overtime visibility, and reminders aligned to local labor rules.
- Skills-to-jobs matcher: connect verified skills and short training programs with employers, without opaque automated rejection.
MVP to try: a simple inventory-and-sales workflow for one specific trade, such as neighborhood repair shops.
Who might sustain it? Business owners or industry associations.
Measure: administrative hours saved, inventory accuracy, and sustained business usage.
Research trail: The SDG Digital Acceleration Agenda includes examples related to decent employment and job quality.
Reality check: Small businesses are price-sensitive and onboarding-intensive. Talk to users before adding features.
SDG 9 — Industry, Innovation and Infrastructure: turn telemetry into action
Connected infrastructure generates data; useful products translate it into operational decisions.
Three software ideas
- Predictive-maintenance starter kit: collect equipment events, detect recurring failure patterns, and schedule inspections.
- Fleet reliability platform: unify vehicle telemetry, service histories, and downtime reporting.
- Infrastructure incident API: standardize reports from field technicians and route them to responsible teams.
MVP to try: start with historical fault logs and maintenance tickets before buying sensors or training ML models.
Who might sustain it? Logistics companies, manufacturers, facility operators, and infrastructure contractors.
Measure: unplanned downtime, mean time to repair, and maintenance cost per asset.
Research trail: ITU's SDG Digital announcement describes digital infrastructure, connectivity mapping, and a set of 34 case studies.
Reality check: Prediction without a repair workflow is just another alert nobody acts on.
SDG 10 — Reduced Inequalities: make services genuinely accessible
A service isn't accessible just because it has a website.
Three software ideas
- Accessibility testing assistant: flag common usability barriers and generate actionable remediation tasks for developers.
- Multilingual public-service guide: explain forms and procedures in multiple languages with source-linked translations.
- Low-bandwidth service portal: provide essential workflows through small pages, SMS, or assisted access points.
MVP to try: audit and improve a narrow class of public-service forms, with real accessibility testing by affected users.
Who might sustain it? Government agencies, service providers, and enterprises with accessibility obligations.
Measure: task completion rates, accessibility issues resolved, and reduced support requests.
Research trail: UNDP: Digital Public Goods for the SDGs explores the role of reusable digital systems in development.
Reality check: Automated accessibility scanners cannot replace testing with real people.
SDG 11 — Sustainable Cities and Communities: help cities operate better
Urban sustainability often comes down to maintenance, mobility, and feedback loops.
Three software ideas
- Transit route analyzer: evaluate vehicle occupancy, service reliability, and route performance.
- Civic maintenance tracker: residents report damaged infrastructure; city teams triage, assign, and close requests transparently.
- Neighborhood resilience map: combine verified data on heat, flood exposure, public facilities, and emergency resources.
MVP to try: one category of maintenance requests in one district, with public status updates and a staff queue.
Who might sustain it? Municipalities, transit operators, or civic organizations.
Measure: issue-resolution time, repeat incidents, and transit reliability.
Case study — civic reporting: FixMyStreet illustrates the idea of turning citizen reports into structured, location-based public-service workflows.
Reality check: A reporting app that the municipality does not respond to can make trust worse.
SDG 12 — Responsible Consumption and Production: keep useful materials circulating
The circular economy needs practical discovery, tracking, and logistics—not just environmental messaging.
Three software ideas
- B2B surplus-material exchange: match usable construction, manufacturing, or packaging leftovers with buyers.
- Repair-history passport: record repairs, parts, and service life to support reuse and resale.
- Waste analytics for restaurants: classify discarded items and identify purchasing or preparation changes.
MVP to try: a narrowly focused exchange for one material type and one metro area, with manual quality checks.
Who might sustain it? Suppliers, recyclers, buyers, or facility operators.
Measure: material reused, disposal costs avoided, and repeat transactions.
Case study — food waste: Too Good To Go demonstrates a consumer-facing circular model, but the same coordination principle can apply to industrial materials (academic analysis).
Reality check: Transport, material quality, and transaction trust may be more expensive than the software.
SDG 13 — Climate Action: measure less, change more
Carbon dashboards are easy to prototype. Trustworthy accounting and verified reductions are harder.
Three software ideas
- Small-business emissions ledger: calculate estimates from energy, fuel, and transport records with auditable factors.
- Building retrofit prioritizer: compare insulation, lighting, and equipment upgrades by cost and expected savings.
- Climate-risk operations planner: translate credible hazard datasets into facility-specific preparedness tasks.
MVP to try: calculate electricity-related emissions for one type of business, exposing the factor source, year, and uncertainty.
Who might sustain it? SMEs, consultants, property managers, and supply-chain buyers.
Measure: independently verified emissions reductions and completed mitigation actions.
Research trail: UN: Global Digital Cooperation and the SDGs outlines how digital technologies can support climate and resource-efficiency work.
Reality check: Estimated emissions are not proof of avoided emissions. Avoid unsupported environmental claims.
SDG 14 — Life Below Water: make marine observations actionable
Protecting oceans requires field observations, enforcement, and collaboration across large areas.
Three software ideas
- Coastal litter mapping: collect geotagged cleanup data and identify recurring pollution sources.
- Fishing-gear recovery network: coordinate reports of lost nets and safe recovery operations.
- Marine monitoring portal: combine public sensor and satellite datasets into understandable local alerts.
MVP to try: one coastline, verified cleanup submissions, duplicate detection, and monthly hotspot reports.
Who might sustain it? Coastal municipalities, research institutions, NGOs, and maritime businesses.
Measure: verified debris removed, recurring hotspots addressed, and response times.
Research trail: The UN digital cooperation report discusses satellite imagery, machine learning, and digital marketplaces for plastic-waste flows.
Reality check: Crowdsourced maps need verification, and removing trash is not the same as preventing new pollution.
SDG 15 — Life on Land: protect biodiversity with better evidence
This goal concerns terrestrial ecosystems, forests, land degradation, and biodiversity—not simply every product involving animals.
Three software ideas
- Habitat-change alert system: combine satellite layers and local observations to flag potentially harmful land-use changes.
- Wildlife rescue case manager: coordinate authorized rescue organizations, veterinarians, and release follow-up.
- Invasive-species reporting app: allow experts to validate sightings and map expansion over time.
MVP to try: an expert-reviewed observation workflow for one region and one species or habitat type.
Who might sustain it? Conservation NGOs, land managers, research groups, or public agencies.
Measure: validated observations, response time, and documented conservation actions.
Case study — UN Biodiversity Lab: UNDP describes the UN Biodiversity Lab as an example of a reusable digital public good supporting environmental data and decision-making.
Reality check: Publishing precise locations of vulnerable species may expose them to harm; location masking and access controls matter.
SDG 16 — Peace, Justice and Strong Institutions: design for accountability
Public-sector software can improve transparency, but trust depends on governance and follow-through.
Three software ideas
- Public procurement explorer: make contracts, amendments, vendors, and spending searchable with clear source links.
- Freedom-of-information request tracker: manage submissions, statutory deadlines, responses, and appeals.
- Legal-aid intake portal: help approved organizations route people to the right services without pretending to provide legal advice.
MVP to try: import a public procurement dataset and build a readable search interface with provenance and update dates.
Who might sustain it? Newsrooms, civil-society organizations, public institutions, and foundations.
Measure: records made accessible, requests resolved, and investigation time saved.
Research trail: The UN digital cooperation report discusses public technologies and e-government as enablers of better services and accountability.
Reality check: Transparency tools need source accuracy, correction mechanisms, and protection against misuse.
SDG 17 — Partnerships for the Goals: coordinate the people doing the work
Partnerships sound abstract until you try to coordinate organizations with different budgets, data formats, and incentives.
Three software ideas
- NGO–company project matcher: connect verified needs with funding, expertise, and volunteer capacity.
- Shared impact-reporting API: help organizations report comparable indicators without duplicate data entry.
- Grant collaboration workspace: manage milestones, evidence, responsibilities, and reporting across multiple partners.
MVP to try: one regional network, standardized project profiles, and a simple matching-and-follow-up workflow.
Who might sustain it? Foundations, networks, corporate social-responsibility programs, and public agencies.
Measure: active partnerships, delivered commitments, and reduced reporting effort.
Case study — Partner2Connect: The International Telecommunication Union's Partner2Connect Digital Coalition uses a public platform for connectivity commitments, progress reporting, and potential partnerships. This is a real example of software supporting coordination—not replacing it.
Reality check: A directory is not a partnership. Track actual commitments and outcomes.
Which ideas make sense for a small software team?
The following is my qualitative assessment, not a validated market ranking. “MVP effort” assumes a focused scope, existing cloud services, and no custom hardware.
| Idea | MVP effort | Potential buyer | Hardest non-code problem |
|---|---|---|---|
| Microbusiness SaaS | Low–medium | Small businesses | Distribution and retention |
| Clinic operations SaaS | Medium | Clinics | Privacy and workflow adoption |
| Food surplus marketplace | Medium | Merchants / partners | Local marketplace liquidity |
| Offline education | Medium | Schools / NGOs | Curriculum and learning outcomes |
| Fleet maintenance analytics | Medium | Fleet operators | Access to clean operational data |
| Water leak analytics | Medium–high | Property managers | Meter integrations and verification |
| Procurement explorer | Low–medium | NGOs / institutions | Data quality and sustainable funding |
| Biodiversity observations | Medium | NGOs / researchers | Expert validation and safety |
A practical four-week validation sprint
Week 1 — Interviews, not architecture. Talk to at least 10 people who experience the problem. Ask about the last time it happened, their workaround, and its cost. Don't pitch features yet.
Week 2 — Prototype the workflow. Build the smallest path from input to action: report → triage → response, or record → alert → verified intervention.
Week 3 — Pilot with real users. Observe people using it. Record where they abandon the flow. Use manual operations behind the scenes if necessary.
Week 4 — Test sustainability. Ask who would pay, approve procurement, provide data, and maintain the system. Agree on one measurable outcome and a next pilot milestone.
Problem → User → Existing workaround → Smallest useful workflow
→ Verified outcome → Buyer / funder → Repeatable delivery
Engineering principles I would keep across all 17 goals
- Offline and low-bandwidth support when access is part of the problem.
- Accessibility and multilingual UX from the first prototype, not the final sprint.
- Privacy by design: collect only the data needed; use retention limits and role-based access.
- Human review for consequential eligibility, health, safety, and legal decisions.
- Interoperability: exports, documented APIs, and open formats reduce lock-in.
- Observable impact: track the real-world outcome, not just clicks or model predictions.
- Operational simplicity: a reliable monolith may be better than an elaborate microservices architecture.
A final thought: don't start with the SDG badge
Start with someone who has a recurring problem. Understand why existing tools fail. Build the smallest thing that changes their day. Then ask which SDG target your measured outcome genuinely supports.
The most useful software for sustainability might not look revolutionary. It might be a reliable scheduling tool for an under-resourced clinic, a better inventory system for a food bank, or a maintenance alert that prevents thousands of liters of water from being wasted.
The goal is not to build 17 apps for 17 goals. It's to build one useful product that works—and can keep working.
What overlooked problem would you build for? And who would be the first person you'd interview?
Further reading and case-study sources
- United Nations — Sustainable Development Goals — official goals and targets.
- ITU & UNDP — SDG Digital Acceleration Agenda showcase — 34 digital solutions, two per SDG.
- UNDP — Digital Public Goods for the SDGs (2023) — five case studies and sustainability considerations.
- United Nations — Global Digital Cooperation and the SDGs — digital technologies across the goals.
- UNEP — Digital Technologies and Food Waste in Kampala — context-specific food waste research.
- Vo-Thanh et al. — Too Good To Go (2021) — peer-reviewed research on social business and mobile apps.
- Too Good To Go case study (2023) — social innovation and food rescue.
- Learning Equality — Kolibri — offline-first education platform.
- MySociety — FixMyStreet — civic issue reporting.
- UNDP — UN Biodiversity Lab — digital public goods for environmental data.
- ITU — Partner2Connect — partnership commitments and tracking.
- GSMA — SDG 17 case studies — utility and cross-sector partnerships.
Disclosure: This is an independently written idea and research guide. The proposed MVPs are hypothetical, and the cited examples do not establish demand, impact, or commercial viability for a new product.
Top comments (0)