Hey, and welcome back to our
series on EC's methodology.

Last time.

We encouraged you to
start by getting a domain.

Today, we're going to cover growth.

Growth potential or scalability
is important to think through.

You don't want to design a
system for 5 million users.

If you're only going to get
5,000 in your first year.

But you also don't want to
design a system for 5,000 users.

If you're likely to get 5 million.

Pretty much everyone we've worked with
targets growth of some sort on some level.

Sometimes that's more users.

Sometimes it's more data,
sometimes it's revenue.

And sometimes it's just
the growth that their users

experience by using their product.

Usually on some level growth
correlates with complexity and cost.

Before you make any decisions about
how you're going to build your app.

You'll want to start mapping out
your user acquisition strategies

so that you can start figuring
out a realistic growth curve.

You don't want to end up building
out $20,000 a month infrastructure

for 500 users doing basic stuff.

It is really easy to fall into a
trap of over-engineering the system.

Conversely though, you don't
want to spin up a $5 server.

That's going to crash as soon as you get
10,000 guaranteed users that are coming

from another part of your business.

It's easy to fall into that sort of
cost reduction trap that leads to

frantic and frankly, expensive fixes.

As with most things, there's
a balance to be struck and you

just need to think it through and
map it out before you get going.

We'd love to learn more about how you plan
for scale and growth in your projects.

Let us know.

And follow us.

If you want to keep up with
this series, we have a lot more,

we're going to share with you.

We're also constantly
updating this process.

As we learn more from ourselves,
our partners and our community.

If you think that we could work together,
we'd love to partner with you and help

you out with your future projects.

Thanks and see you next time.