* are required before work begins.
Everything else can be filled in as we go.
Progress
0%
0 of 0 required fields
01
About your organization
Basic information that feeds your homepage copy, local SEO schema, and Google Business Profile.
1.1 Legal organization name *
1.2 Preferred display name on website (if different)
The name you want on the website — may be shorter or more conversational than the legal name.
1.3 Organization type *
1.4 Primary phone number *
1.5 Primary contact email *
1.6 Full street address *
Must exactly match your Google Business Profile for local SEO. Include suite number if applicable.
1.7 EIN / Tax ID number
Displayed on donation pages for donor tax receipts.
1.8 Year founded
1.9 Office / service hours *
List all days. For churches, include all service times. Used in schema markup and contact page.
1.10 In one or two sentences, what does your organization do and who does it serve?
Write this as you would say it to a first-time visitor — not your formal mission statement.
1.11 What makes your organization different from others doing similar work?
Be specific — geography served, populations focused on, unique programs, history, community trust.
02
Mission & website goals
What do you need this website to accomplish? These answers determine what we build first.
2.1 What is the single most important thing this website should do? *
2.2 What does success look like 6 months after launch?
Be concrete — "more donations" is not measurable. "10 new online donations per month averaging $75" is.
2.3 What are the top three problems with your current website? (or "we have no website")
2.4 Websites you admire — even outside your sector *
Share URLs. Note what specifically you like: layout, tone, photography, how they present their mission.
2.5 Websites you strongly dislike
Just as useful — knowing what to avoid is half the design brief.
2.6 Do you have an existing style guide, brand guidelines, or annual report we should reference?
03
Audience & community
Who visits your site and what are they trying to do? The site design and copy shift significantly based on your answer.
3.1 Who are your primary website visitors? (check all that apply)
3.2 Describe the person you most want to reach with this website
Age range, situation, what they're searching for, what they need to feel or understand before they take action.
3.3 Do you serve any specific populations or communities?
3.4 What geographic area do you serve?
04
Programs, services & content
What pages do we need and what content do you already have? This section builds your site map.
4.1 List all programs and services you want on the website *
Each major program typically gets its own page for SEO. List everything — we'll decide together what merits a dedicated page.
4.2 Which pages do you need? *
4.3 Do you have existing written content we should use?
4.4 Do you have professional photos of your team, facility, and community?
Photo consent note
Any photos of beneficiaries, clients, or minors on the website require written photo release forms. Please confirm these are on file before submitting images for publication. I will not publish identifiable photos of minors without confirmation of consent documentation.
4.5 Do you have an existing logo?
4.6 Do you have testimonials, impact stories, or community quotes we can use?
First names or pseudonyms only for beneficiaries. No identifying details without written consent.
05
Design & brand
Your visual direction. Even rough answers here save significant revision time later.
5.1 How would you describe the feeling you want your website to convey?
5.2 Existing brand colors
Hex codes if known, or describe: "royal blue and gold", "forest green and cream".
5.3 Colors you absolutely do not want on your website
5.4 Any other design notes, preferences, or things to avoid?
06
Technical & integrations
Existing accounts, tools, and third-party services that need to connect to the new site.
6.1 Do you have an existing domain name? *
Where is it registered? (GoDaddy, Namecheap, Google Domains, etc.)
Do you have login access?
6.2 Existing hosting provider and access level
6.3 What tools and integrations do you need on the new site? *
6.4 Do you currently use a CRM or donor management system?
e.g. Salesforce Nonprofit, Bloomerang, DonorPerfect, Planning Center, Church Management Software
6.5 Do you have an active Google Business Profile?
07
Donations & fundraising
How donations flow through your site determines how we build this section.
Payment processing note
Donation payment data must never be stored in WordPress. We will use GiveWP, Stripe, or PayPal Giving Fund to handle all payment processing. I will never build a raw credit card form inside WordPress.
7.1 Do you currently accept online donations?
7.2 What donation tool do you want to use (or currently use)?
7.3 What types of giving do you need to support?
7.4 Do donation confirmation emails need to include tax receipt language?
7.5 Are there any specific fundraising campaigns or drives we should plan pages for?
08
Compliance & legal
Specific to nonprofits and churches. Your answers determine how we build certain pages.
Your responsibility
I will build the pages and publish the content you provide. You are responsible for supplying all required legal pages and ensuring the accuracy of your organization's disclosures, financial information, and program descriptions. I am not a lawyer and cannot review your content for legal sufficiency.
8.1 Which legal and compliance pages can you supply copy for before launch? *
You supply the copy — I format and publish. These should be reviewed by your attorney or accountant.
8.2 Does your organization work with children or minors in any programs?
If yes on 8.2:
Any organization working with minors should link their safeguarding or child protection policy from the website. This is both a trust signal and a liability protection measure. I will flag this section during the build and ask you to provide the policy document.
8.3 Do you broadcast or post worship music on your website or live stream?
CCLI streaming license note
If you broadcast or post videos containing copyrighted worship music, a CCLI streaming license is required for most churches. This is your responsibility to confirm and maintain — I will flag any content that may require it, but I cannot verify your licensing status.
8.4 Do you want to display before/after stories, impact photos, or named beneficiary testimonials?
09
Timeline & final notes
Deadlines, decision-makers, and anything else I should know before we start.
9.1 Is there a specific date you need the site live by? *
9.2 How quickly can you turn around feedback on design drafts?
9.3 Who needs to approve the website before it goes live?
Knowing decision-makers upfront prevents launch delays. Be specific about who has final say.
9.4 Who will manage the website after launch?
This affects how I build the admin experience — simpler for volunteers, more robust for staff.
9.5 Preferred communication during the project
9.6 Are you interested in a monthly maintenance plan after launch?
9.7 Anything else I should know before we start?
What happens next
Once you return this questionnaire I'll review your answers within 48 hours and send a kickoff summary confirming scope, timeline, and your content checklist — everything you need to gather before we start building. Your Notion project portal will be live within 24 hours of receipt.
Ready to submit?
Your answers save automatically as you type. Click "Save as PDF" to print or save a copy for your records, or "Copy all answers" to paste into an email reply.