# An EdTech platform on a non-profit budget

By Venus Paneliya, full-stack AI engineer. Category: Cloud. Originally posted on LinkedIn.

A non-profit founder needed an EdTech platform built.

Budget was tight.

Here's how we made it work.

The founder had a clear vision.

An online learning platform for kids with interactive math exercises, progress tracking for teachers and parents, and community features.

The budget was a fraction of what most agencies would quote.

Most developers would have said, "Cut features."

I said, "Let's prioritize differently."

We started by identifying the three features that mattered for launch.

- Feature 1: The core learning experience. Interactive math exercises that kids could complete independently. If this didn't work well, nothing else mattered.

- Feature 2: A teacher dashboard. Simple progress tracking showing which students completed which exercises and where they struggled. Not a full analytics suite. Just enough to know who needed help.

- Feature 3: Parent access. A read-only view of their child's progress. No editing. No complex permissions. Just visibility.

Everything else went onto a post-launch list.

- Community features
- Gamification
- Advanced analytics
- Notification system

Good ideas.

Not launch-critical.

Then we made architecture decisions that reduced cost without compromising quality.

- Serverless infrastructure. Resources scaled with usage, cutting infrastructure costs by roughly 60-70% compared to traditional hosting.

- Simple authentication. No social login. No SSO. Just secure email and password authentication, saving about a week of development time.

The platform launched on time.

Infrastructure costs stayed under $50 per month for the first 500 users.

The foundation was solid enough that adding features later didn't require rebuilding.

Here's the lesson.

Tight budgets force better architecture decisions.

When you can't afford to build everything, you're forced to build the right things.

And when infrastructure costs matter, you choose architectures that scale efficiently instead of architectures that are simply easy to set up.

Constraints aren't limitations.

They're design inputs.

Have you ever built something on a tight budget that turned out better because of the constraint?

Canonical: https://venuspaneliya.com/writing/edtech-on-a-non-profit-budget/