Craftjd Compare

One person stays after launch. That work is already covered.

Most owners land with an agency, a freelancer who has moved on, or a builder they run themselves. Pick the path that feels closest. I’ll walk the tradeoffs with you on what actually matters: who stays, what a change costs, and whether you end up managing the site instead of the business.

Which path are we looking at?

Tap the one that matches your situation. The side-by-side opens underneath.

Agency vs this model

The right call when you need a full team or work that goes well beyond a site. If what you need is a solid site that keeps evolving without another invoice for every ask, this model stays lighter on purpose.

Agency This model

Getting started

Agency

Proposal, discovery, then a build invoice

This model

Free to launch. Typically live in 14–21 days.

Ongoing cost

Agency

Pay for the build, then pay again to maintain it

This model

$90/mo. Hosting, updates, and security included.

Who you talk to

Agency

Account managers between you and the work

This model

One developer builds it and stays with it.

When something changes

Agency

The ask feels costly: tickets, scope, billed hours

This model

Email a request. Same person handles it. Already covered.

Leaving

Agency

Proprietary platforms make walking away expensive

This model

Cancel anytime. A full site/code handoff is a separate one-time fee.

Freelancer vs this model

Fine when you only needed a one-time deliverable and you are ready to own what comes next. If you would rather not inherit a quiet site with no one on the other end, I stay after launch.

Freelancer This model

Getting started

Freelancer

Fixed project fee; timing depends on their other clients

This model

Free to launch. One person, clear timeline.

After launch

Freelancer

Availability ends with the final deliverable

This model

The same arrangement continues. Requests just get smaller.

When something changes

Freelancer

Nobody left to ask, so the site stops evolving

This model

Email a change. Same person who built it handles it.

Security & backups

Freelancer

Usually not included once the project closes

This model

Monitoring, SSL, and nightly backups are in the fee.

Leaving

Freelancer

You inherit whatever was left behind

This model

Cancel anytime. A full site/code handoff is a separate one-time fee.

Self-serve vs this model

A good fit when you enjoy the tool and still have time after serving clients. If keeping the site current has become a second job, I take that work so you stay on the floor.

Self-serve This model

Monthly fee

Self-serve

Cheaper per month on paper

This model

Free to launch. $90/mo. Your hours are not on the invoice.

Who makes changes

Self-serve

You, inside the builder, on evenings and weekends

This model

You send direction. One developer implements it.

Your time

Self-serve

Managing the site costs more than the subscription

This model

You stay with clients. Site work stays with me.

What you can build

Self-serve

Locked into whatever the template allows

This model

Built around how your business actually works.

Leaving

Self-serve

Moving off a builder is often a painful DIY migration

This model

Cancel anytime. A full site/code handoff is a separate one-time fee.

Next step

Try the demo

Either way, you’ll hear back from a real person. No automated funnel.

Site inquiry

Step 1 of 3

What you do, who you serve, and where the site stands today.

Your business or service in plain terms. Not a tagline.

The people or businesses that hire or buy from you.

Where are you with a website right now?