How to Price Donation-Form Setup as a Service

You are selling two things, price them separately

The single biggest pricing mistake is bundling everything into one number. There are two distinct products here:

• The setup — a one-time piece of work: branding the form, connecting the client's Stripe, embedding it, and handing it off with training.
• The care plan — an ongoing monthly service: keeping it live and on-brand, a capped number of edits, the occasional campaign page, a light performance check-in.

Price them as two line items. The setup is your front door and it should stand on its own. The care plan is the recurring revenue, and it is also your defense against scope creep, because it gives you a place to put all the "can you just" requests that would otherwise be free. The full business case for the recurring side is in donation forms as an agency recurring-revenue stream.

Price on value, not on the hour you spent

Embedding a modern inline form genuinely is fast — sometimes under an hour of hands-on work. That is exactly why hourly pricing is a trap here. If you bill the hour, you are punished for being efficient, and the client anchors to "it only took an hour, why am I paying $500."

You are not selling an hour. You are selling a working donation system on the client's own Stripe that brings in money, looks like their site, and they did not have to figure out. Price that on its value. A donation form that pulls in even a few thousand dollars a year makes a $500–$1,500 setup fee obviously reasonable, and that is the comparison you want the client making — fee against donations raised, not fee against your effort. The fast setup is your margin, not the client's discount.

Sample price tiers

Here are realistic, deliberately middle-of-the-road tiers for a small-to-mid agency or freelancer. Adjust for your market — coastal-city pricing runs higher, and an established agency commands more than a new freelancer.

Notice the setup fees are not tiny. They are anchored to the value of a working giving system, not to the twenty minutes of embedding. The care plans scale with how much ongoing attention the client wants. For where these numbers sit inside a wider service menu, see the agency guide to donation forms on client sites.

What to include, and what to explicitly exclude

The exclusions matter as much as the inclusions, because the unstated parts are where margin leaks. Write both down in the proposal.

Include in setup: branding the form to the site, connecting the client's Stripe, setting suggested amounts and the recurring option, embedding on the main donate page, a handoff walkthrough, and a test donation together.

Exclude from setup (or bill separately):

• The client's Stripe account verification and bank issues — that is between them and Stripe.
• Additional campaign or landing pages beyond the first.
• Ongoing copy and amount changes after handoff — that is the care plan.
• Integrations with a CRM or email tool the client uses.
• Design changes to the surrounding page after sign-off.

Stating these is not being stingy. It is the difference between a client who respects the boundary and one who treats every future request as covered by the original fee.

How to frame it to a budget-conscious nonprofit

Nonprofits are price-sensitive and a little guilt-prone about spending on overhead. Frame the cost the right way and the objection mostly disappears.

• Frame it as revenue, not cost. "This is the part of the site that brings money in." A donation system is not overhead; it is the fundraising tool.
• Use their own numbers. If their old setup raised X, a better-converting on-brand form that keeps donors on-page can plausibly raise more. The setup fee is small next to a year of giving.
• Make the care plan about peace of mind. "Someone competent is watching the donate button so a board member never discovers on December 30th that gifts stopped landing." That sells itself.
• Be transparent about processing fees. Explain Stripe's 2.9% + 30¢ and the 2.2% + 30¢ nonprofit rate up front so there are no surprises and you look like the honest one.

The scope-creep traps to watch

A profitable donation add-on dies by a thousand small favors. The common traps:

1. "Can you just add another amount." Fine once. But if it has no edit limit, you are now their part-time staff. This is what the care plan's capped edits are for.
2. "It stopped working." Nine times out of ten it is a Stripe account issue on their side — an ignored verification email. Help, but make clear it is their account, billable beyond the plan.
3. "Can we do a quick campaign page." A campaign page with goal tracking is real, scoped work, not a quick favor. Quote it.
4. The unpriced redesign. The client redesigns the page and the form needs re-placing. Scoped work.

The defense for all of these is the same: a tight written scope plus a care plan that gives the small stuff a home. And the quieter defense is picking a low-maintenance setup in the first place. If you choose a branded inline embed on the client's own Stripe — the kind of setup KindLumen is built for — there is very little that breaks unprompted, which means your care plan is mostly margin instead of mostly firefighting. You can see that setup on the pricing page. Pick the tool with the shortest support tail and your pricing actually holds up.