CASES
NGO WordPress CRM Agency

NGO Website with Tailored CRM in WordPress

How an agency founder built wmd.org.pk — a 79-widget, fully functional NGO website — in 12 days through conversation with WPCursor.

Step 1: Foundation & Audit

Asad pointed WPCursor at WMD's existing WordPress site and said: "Please check all the pages, widgets, everything. The name is We Make a Difference, WMD."

WPCursor browsed the site, audited every page and widget, then Asad uploaded a detailed implementation brief. The AI saved it as organisational knowledge, generated a complete sitemap, and started cleaning up the old structure.

Within hours, pages were scaffolded — home, about, programs, campaigns, donate, contact, volunteer, team, impact stories. But Asad pushed immediately. He found broken links, non-functional single pages, and missing dynamic content. He asked WPCursor to build a CRM dashboard — right there, in the same conversation.

By end of Day 1: 20+ widgets, a basic CRM, and a long list of things still to build.

  • Five core programs each containing multiple active campaigns
  • Impact stories designed to drive donations
  • Volunteer registration with Pakistan-specific fields (CNIC, city)
  • Case submission forms for families in need
  • Detailed team profiles with co-founder emphasis
  • Mobile-first design for a Pakistani audience
  • A custom CRM dashboard to manage all submissions
Foundation & Audit

Step 2: Content Integration

Days 2–6 were about feeding the site real content. The client had organised material in Google Drive — team photos, campaign documentation, program details, impact stories. Asad connected the Drive:

"In my drive Ahmad shared WMD data — it's all about WMD. Pull everything relevant to the current website and then add pictures and content accordingly."

This phase revealed the core complexity of nonprofit websites: deeply interconnected content. A program contains campaigns. Campaigns have donation CTAs. Impact stories connect back to programs. Team members are tied to specific initiatives. Getting all these relationships working dynamically — powered by custom post types, not hardcoded pages — required dozens of widget iterations.

  • Basic Human Needs — food drives, Ramzan Rashan, winter relief
  • Education — scholarships, school support, literacy programmes
  • Health — medical camps, medicine distribution
  • Disaster Management — emergency response across multiple cities
  • Community Outreach — orphan support, family assistance
Content Integration

Step 3: Programs, Campaigns & Team

February 1st and 2nd were the most intensive sessions — 238 and 215 API interactions. The conversations were relentless:

"Program page and single program page is still not acceptable. Add more images from Drive accordingly."

"Recheck programs and single programs, make it functional, internal campaigns functional."

Pages were rebuilt multiple times. The program grid went through three versions. Campaign cards were redesigned. Single campaign pages got richer with each pass.

Team profiles demanded the same precision. The three co-founders needed to stand out from regular team members — but tastefully:

"Cofounders are the main persons of WMD and they should look different."

"It's too much favouritism. Just give her a touch wisely, not the old typical story everywhere."

The team page went through four iterations before the balance was right.

  • Program archive with dynamic campaign counts
  • Single program pages with full campaign listings
  • Campaign cards with progress tracking and donation CTAs
  • Single campaign pages with images, stories, and volunteer flows
  • Team archive with co-founder distinction
  • Single team member profiles
Programs, Campaigns & Team

Step 4: Mobile, SEO & Polish

February 3rd: mobile responsiveness and final polish. Asad found the mobile header wasn't working, the logo wasn't displaying, navigation needed restructuring. He spent 38 messages in one session on the mobile menu alone.

The final sessions covered everything that separates a functional site from a finished one: SEO meta tags across all pages. FAQ content from organisational knowledge. Spacing and visual consistency. Performance optimisation. Removing duplicate images from the media library.

Visual review was constant throughout. "Check visually." "Browse it." Asad couldn't read code — he needed to see results in a browser to give feedback. The design emerged through use, not from a Figma file. No mockups. No design spec. Just a founder with taste, iterating in real time.

  • 79 custom widgets total
  • 12,310 lines of HTML templates
  • 26,694 lines of CSS
  • 3,541 lines of JavaScript
  • 43 interactive widgets with JS
  • 19 widgets with dynamic data sources
  • 30 conversations, 436 messages, 12 calendar days
Mobile, SEO & Polish

Step 5: One Founder. One Tool. Full Delivery.

The traditional agency model for a project like WMD: discovery, proposal, wireframes, mockups, client feedback, revisions, development handoff, QA, content entry, launch. Six to eight weeks. A designer, a developer, a project manager.

Asad compressed that into 12 days of direct conversation. Not because he cut corners — the final deliverable has 79 custom widgets, 42,000+ lines of code, dynamic content architecture, form processing, and a full CRM. He compressed it because the bottleneck in agency work was never the ideas or the direction.

It was the translation layer — turning what the creative director sees in their head into something a developer can build. WPCursor removed that layer.

Asad directed like a creative director, not a developer. He never wrote a line of code. "Every campaign should lead to donation and getting volunteers." "These are the people who made this happen — show them with heart." "Make it appeal to donate."

Directives, not code. Vision, not specs. One agency founder. One tool. Full delivery.

  • One person delivered a project normally requiring 3+ roles
  • No developers on the project
  • No Figma handoff or design mockups
  • Full dynamic content architecture with custom post types
  • Custom CRM dashboard built mid-project on request
  • Client can self-manage and update everything post-launch
One Founder. One Tool. Full Delivery.
Step 1