← Back to the problem

The builder's path

Five steps from a problem to its solution.

For: Small organizations can't see what their website costs a visitor on a slow or metered connection.

“Some things are under our control, while others are not under our control.”
Epictetus · Enchiridion 1 (tr. W. A. Oldfather)

Routes to a solution

Six ways to take this forward

Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in Canada.

  1. Step 1

    Build in the open

    Publish the code and invite contributors from the community.

    • Code for Canada ↗

      Civic tech: technologists working with governments on public services.

    • Canadian Digital Service ↗

      Builds federal public services in the open; a route for problems with government services.

    • Community Futures ↗

      Local offices across rural Canada with small business loans and advice; in Atlantic Canada they are called CBDCs.

    • Mila ↗

      Quebec's AI institute in Montreal; partners with organisations on applied AI projects.

  2. Step 2

    Fund the maintainers

    Sponsors, collectives and open source grants.

    • Code for Canada ↗

      Civic tech: technologists working with governments on public services.

    • Canadian Digital Service ↗

      Builds federal public services in the open; a route for problems with government services.

    • NRC IRAP ↗

      Advice and funding for technology innovation in Canada.

    • Mitacs ↗

      Funded research internships linking students with organisations.

  3. Step 3

    Get it adopted

    Civic tech groups and public bodies take it up.

    • Code for Canada ↗

      Civic tech: technologists working with governments on public services.

    • CanadaBuys ↗

      Where the federal government posts its tenders; search by region and category.

    • Innovative Solutions Canada ↗

      Federal departments post challenges and fund small businesses to solve them, then buy the result.

    • BDC ↗

      The federal business development bank: loans, advice and venture capital.

What this problem needs

Ideas, sources and tools for this problem, from first interviews to funding.

  • Web
  • Accessibility
  • Analytics
  • Mobile

Ideas to explore

  • Idea 1Run Lighthouse, translate the resultUse the PageSpeed Insights API to get the transfer sizes, then show them as dollars and seconds for the visitor's plan instead of a score.
  • Idea 2Before-and-after reportLet a site owner save a check, fix images, and re-run to see the saving in MB and dollars.

Specific to this problem

Talk to first

Starter prompt

Built from this problem's brief. Paste it into Claude or any AI assistant.

Help me design and build a first working prototype for this problem in Canada.

Problem: Small organizations can't see what their website costs a visitor on a slow or metered connection.
Who it hurts: Volunteers and staff who run websites for community groups, town councils and small businesses.
The moment it hurts: When someone outside a town on a capped mobile plan tries to load a notice and the page stalls.
What people do today: Audit tools report scores and milliseconds on a simulated phone, which many site owners can't turn into a decision.
Why it is still unsolved: Page weight keeps growing, and most site owners never see it in terms of time or money for their own visitors.
What solved looks like: A free page where someone enters a web address and sees total download size, the cost at a per-GB rate they enter, load time at 5, 10 and 50 Mbps, and the three biggest files to fix first. Totals match browser developer tools within 10% on 10 real sites.
Where: Canada

First, list what you would need to learn from the people affected before building, as interview questions.
Then propose the simplest version that would help, the screens or messages it needs, and the data it would use.
Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.
  1. Understand it

    Talk to the people who live it before you build.

    “The true creator is necessity, which is the mother of our invention.”
    Plato · Republic II, 369c (tr. B. Jowett)
  2. Prototype with AI

    Get a working version in front of people fast.

    Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.

    “The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
    Ada Lovelace · Notes on Menabrea's Sketch of the Analytical Engine, Note A (1843)
  3. Find the data

    Open data that fits this problem.

    “Lead me from the unreal to the real, from darkness to light.”

    असतो मा सद्गमय। तमसो मा ज्योतिर्गमय।

    asato mā sad gamaya, tamaso mā jyotir gamaya

    Bṛhadāraṇyaka Upaniṣad · 1.3.28
  4. Build it

    Tools matched to what this problem needs.

    “A journey of a thousand li starts beneath one's feet.”
    Laozi · Tao Te Ching 64
  5. Launch and get support

    Ship it responsibly, and find help and funding.

    “Your right is to the work alone, never to its fruits.”

    कर्मण्येवाधिकारस्ते मा फलेषु कदाचन

    karmaṇy evādhikāras te mā phaleṣu kadācana

    Bhagavad Gītā · 2.47

Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.