Salesforce implementation for associations and nonprofits

Salesforce your team will still understand in three years.

Most implementations are judged on launch day. We build for year three: every feature traced to a numbered need, standard Salesforce before anything custom, a plain-English manual, a record of every change, and admins of your own who have already run it.

Book a conversation See a build come together

80+Salesforce implementations behind the method
EveryFeature traced to a numbered requirement and the person who raised it
2Of your own admins run the real tasks before we call it done
1Blended rate, whoever on the team does the work

What a build looks like

Six systems become one record, one sprint at a time.

Maria Lopez is a member, a donor and a regular at Lakeview Association's conference. Today she lives in six places. Here is how that changes, and what gets written down along the way.

Before the build
Maria lives in six places.
Her membership, gifts, registrations, emails, payments and CE credits sit in six systems. Nobody sees all of her at once, and nobody is sure which copy is right.
Sprint 1
Membership and giving join one record.
R-001 and R-002 connect the membership system and the donor database to Maria's record. The sprint ends when your directors approve the demo, and the release and its manual pages are written down.
Sprint 2
Events and email follow.
R-003 and R-004 bring her event registrations and email preferences onto the same record. Same rule: demo approved, release logged, manual pages written.
Sprint 3
Payments that finance can reconcile.
R-005 connects the finance system, so dues, payments and refunds on Maria's record match the books. Your finance director approves the demo.
Sprint 4
The spreadsheet retires.
R-006 puts CE credits on the record. The spreadsheet that tracked them is retired, and the manual says why, so nobody quietly starts a new one.
Handed over
One record, and the file that explains it.
Six requirements, four releases on the record, six manual pages. Your team can say what is running, why it exists and who approved it.

Sprint 1✓Demo approved

Sprint 2✓Demo approved

Sprint 3✓Demo approved

Sprint 4✓Demo approved

Systems Lakeview runs today

SALESFORCE RECORDMaria LopezMember and donor, Lakeview AssociationHanded over

Membership systemR-001RetiredMembers, renewals, chaptersRaised by Director of Membership

MEMBERSHIPNot connectedRenews Aug 31, Chicago chapter

Donor databaseR-002RetiredGifts, appeals, tributesRaised by Director of Development

GIVINGNot connectedSpring appeal gift, plus a soft credit

Event registrationR-003RetiredConference and webinarsRaised by Events Manager

EVENTSNot connectedRegistered for the fall conference

Email platformR-004RetiredNewsletters and remindersRaised by Communications Manager

EMAILNot connectedRenewals and chapter news, opted in

Finance systemR-005RetiredDues, payments, refundsRaised by Finance Director

PAYMENTSNot connectedDues paid, reconciled with finance

SpreadsheetsR-006RetiredCE credits, kept by handRaised by Director of Education

CE CREDITSNot connected12 CE credits this cycle

Handover file

RELEASE RECORD

Nothing released yet

Release 1R-001, R-002Approved by Membership and Development

Release 2R-003, R-004Approved by Events and Communications

Release 3R-005Approved by Finance

Release 4R-006Approved by Education

SYSTEM MANUAL

No pages yet

p. 1Renewals and the 30-day grace period

p. 2Gifts and soft credits

p. 3Event registrations on the record

p. 4Email preferences and opt-outs

p. 5Payments and refunds, and how they reconcile

p. 6CE credits, and why the spreadsheet retired

Traceable

Every feature has a number, and a person behind it.

Nothing is built on a vague wish. Each feature traces to a numbered requirement in the register, and to the person who raised it. Three years on, you can point at anything in Salesforce and find out why it is there.

If you have a Blueprint, the register already exists and we build from it
Work without a requirement number stops for a conversation
Scope changes come through one door: a numbered change request, approved by your named approver before any work starts

Requirements register · Lakeview Association

R-001Members, renewals and chapters on one recordRaised by Director of MembershipRelease 1

R-002Gifts and soft credits on the same recordRaised by Director of DevelopmentRelease 1

R-005Payments and refunds that reconcile with financeRaised by Finance DirectorIn sprint 3

R-007Monthly report produced in a day, not threeRaised by Executive DirectorSpecification

CR-003 · Add a 7-day renewal reminderRaised by Membership Coordinator · 6 hours, no change to datesFor your approver

Standard first

We challenge every custom request.

Custom builds are where long-term cost and risk hide: they need someone who remembers how they work, and they can break when Salesforce updates. So every request is first held up against what Salesforce already does as standard.

If Salesforce does it as standard, we configure it rather than write it
When custom is the right answer, we say why, and the reason goes in the manual
Fewer moving parts for your admins to look after, and for any future partner to learn

Standard first review · Lakeview Association

R-001Renewal reminders at 90, 60 and 30 daysAsked for: custom codeSalesforce already does this with a scheduled automation. No code to maintain.Standard

R-002Soft credits for household giftsAsked for: a separate appSoft credits are built into Salesforce. Configured, not coded.Standard

R-008Split dues between national and chapterNo standard feature fitsBuilt custom, approved by Finance, explained on manual page 9.Custom, documented

Written down

A manual in plain English, and a record of every change.

Two deliverables most builds skip. The system manual says what each automation does, why it exists and who approved it. The release record logs every change, so nobody is ever unsure what is actually running.

System manual · page 1

Renewals and the 30-day grace period

R-001Release 1Automation

What it does: Sends reminders 90, 60 and 30 days before a member's renewal date, stops the moment they renew, and keeps the membership active for 30 days after it lapses.
Why it exists: Members were lapsing because reminders depended on someone remembering to send them.
Who approved it: Director of Membership, at the Sprint 1 demo.
How to change it: The grace period is a setting your admin can change. No code.

Release record · Lakeview Association

ReleaseWhat changed, and whyApproved by

Rel 1Mar 14Members and donors on one recordR-001, R-002Directors of Membership and Development

Rel 2Mar 28Event registrations and email preferencesR-003, R-004Events and Communications

Rel 3Apr 11Payments and refunds reconcile with financeR-005Finance Director

Rel 4Apr 25CE credits on the record, spreadsheet retiredR-006Director of Education

Rel 5Jun 6Grace period changed from 30 to 45 daysCR-009After launchDirector of Membership

Handover

Tested by doing, not by watching.

You name two admins. Before we call the build done, they run the real tasks themselves, in your Salesforce, with the manual open. If they can't, it isn't finished.

Two people, so knowledge never lives in one head
Real tasks from your year, not a training script
Anything they stumble on is fixed in the system or in the manual

Handover check · Lakeview Association

Task, run by your adminsMembership CoordinatorDevelopment Associate

Add a chapter and move members into it✓✓

Change the renewal grace period✓✓

Record a gift with a soft credit✓✓

Process a refund that finance can reconcile✓✓

Run the quarterly funder report✓✓

Explain one automation from the manual✓✓

Handover complete: both admins, every taskSigned off by the Director of Membership

What we build on Salesforce

Everything your organization runs, on one Salesforce.

From the record underneath to the portals and agents on top: twelve areas we design and build for associations and nonprofits, each shown as it looks at Lakeview Association.

01 · Records and relationships

People, households, organizations and chapters, modeled once.

Each person has one record that knows their household, their employer and their chapter, and every chapter rolls up to the national organization.

Relationships · Maria Lopez

PARENTLakeview AssociationNational, 2,948 members

CHAPTERChicago Chapter412 members

HOUSEHOLDLopez HouseholdMaria and Daniel Lopez

PERSONMaria LopezMember, donor, volunteer

ORGANIZATIONHarbor ClinicEmployer, organization member

One person, one record. She counts once in her household's giving, once in her chapter and once in the national total.

02 · Membership and dues

Joins, renewals, grace periods and reinstatement, as rules.

Member types, terms and dues, with lapse and reinstatement rules your admins can read and change, not exceptions someone has to remember.

Membership · Maria Lopez

Professional memberAnnual term · Chicago Chapter

Active

JoinedSep 2019, Student
UpgradedJun 2021, Professional
RenewedAug 2025, online
Renewal dueAug 31
Grace endsSep 30

DuesProfessional, annual, split national and chapter

Lapse ruleLapses after a 30-day grace period

ReinstatementWithin 90 days keeps the original join date

03 · Fundraising and grants

Gifts credited right, grants reported on time.

Gifts, pledges, recurring giving and soft credits, and grants tracked from the first inquiry to the final report, with the deliverables attached.

Grant · Rural Clinic Fellowship

Rural Clinic FellowshipFunder: Midwest Health Fund · two-year grant

Interim report Nov 15

Inquiry
Application
Awarded
Interim report
Final report

DELIVERABLES, FROM PROGRAM RECORDS

Fellows placed in rural clinics10 of 12

Patient visits logged by fellows3,214

Mentor check-ins completed58 of 60

The interim report runs from the same records the program team works in. Nobody rebuilds it in a spreadsheet.

04 · Events and education

Registrations, sessions and credits, on the record.

Conferences, webinars and courses, with attendance and continuing education credits posted to each person when check-in closes.

Fall Conference · sessions and credits

Fall ConferenceOct 14 to 16 · 512 registered

Check-in closed

SessionCreditsAttended

Opening keynote1.0 CE486

Ethics in practice1.5 CE212

Clinical documentation2.0 CE174

Chapter leaders forumNone58

Credits posted to 497 member records. Certificates and updated transcripts went out the same day.

05 · Portals and self-service

Members, donors, volunteers and chapters serve themselves.

A secure site where people renew, register, update their details and download receipts and transcripts, and chapter leaders manage their own roster.

Member portal · Lakeview Association

Lakeview AssociationMembershipEventsLearningGiving

Welcome back, Maria

MEMBERSHIPActive, renews Aug 31Renew now

EVENTSFall Conference, registeredAdd a session

LEARNING12 of 18 credits this cycleDownload transcript

GIVINGSpring appeal giftReceipt ready

Update my detailsChicago ChapterVolunteer sign-ups

06 · Integrations

Payments, accounting, email, events, website and learning, connected.

Each connection has a direction, a schedule and one system that owns each field, and you can see that it ran.

Integrations · Lakeview Association

Payment processorInto Salesforce · instant

Website formsInto Salesforce · instant

Learning systemBoth ways · hourly

HUBSalesforceOne record per person

AccountingOut of Salesforce · nightly

Email platformBoth ways · every 15 min

Event platformInto Salesforce · hourly

6 of 6 healthyLast run 6 minutes ago · each field owned by one system

07 · Automation and workflow

Approvals, routing and follow-ups that run on readable rules.

The steps your team repeats every week, automated, with every rule written down and the timings set by your admins.

Workflow · new membership application

WHENA membership application is submitted

CHECKIs a student rate requested?

Yes

ASSIGNMembership Coordinator verifies enrollment within 2 days

DOApprove, send the welcome email, add to the chapter

THENWelcome call task for the chapter, 7 days later

The 2 days and the 7 days are settings your admin can change. No code.

08 · Reporting and dashboards

Dashboards each team trusts, and leadership does too.

Built on definitions agreed with your team, so "active member" and "renewal rate" mean the same thing in every report.

Membership dashboard · October

Active members2,948

Renewal rate89%

New this quarter214

In grace period63

RENEWAL RATE BY MONTH, AXIS FROM 70%

Target 90%

84%Jun86%Jul91%Aug93%Sep88%Oct

Active member: dues paid, or inside the 30-day grace period. Written once, used everywhere.

09 · Data quality

A record that stays clean after launch.

Duplicate rules, validation and a monthly health check, so problems are caught at entry rather than found at year end.

Data health · October

FIELDS FILLED IN, ACROSS 2,948 MEMBERS

Email98%

Chapter96%

Renewal date100%

Mailing address92%

Employer81%

Duplicate ruleSame email, or same name and postcode, stopped at entryOn

Employer below 90%List of 560 members sent to the Membership teamFor review

10 · Security and access

Each team and chapter sees what it should.

Roles, permissions and sharing designed with you, so chapter leaders see their own members and finance data stays with finance.

Access · who sees what

RoleMembersGiftsPaymentsCases

Membership CoordinatorEditViewViewEdit

Development AssociateViewEditViewNone

Finance DirectorViewViewEditNone

Chicago chapter leaderOwn chapterNoneNoneNone

VolunteerOwn recordNoneNoneNone

Chapter leaders see their own members because of a sharing rule, not because someone trusted them with everything.

11 · Service and case management

Every question in one queue, answered on the record.

Questions arrive by email, web form or portal, are routed by topic and tracked to an answer, with the history on the person's record.

Member services · today

Member services queueRouted by topic · 4 open, 11 answered today

C-0412Can't sign in to the member portalMaria Lopez · Membership teamAnswered

C-0413Receipt for my spring giftDaniel Lopez · Donor servicesAnswered

C-0414Transfer to the Denver chapterAna Ruiz · Membership teamWith the chapter

C-0415Credit missing from my transcriptJames Okafor · EducationIn progress

Every case sits on the person's record, so whoever helps next sees the whole history.

12 · AI and agents

Agents that work inside the limits you set.

Assistants for staff, members and donors that draft and suggest from one clean record, with a person reviewing before anything goes out.

Agent settings · member questions

Member questions agentPortal and email · limits set by Lakeview

Reviewed by Membership

CAN SEE

Membership status, registrations, credits, receipts

CAN DRAFT, FOR REVIEW

Replies, event registrations, receipt resends

NEVER

Change dues, issue refunds, delete a record

ALWAYS HANDS TO A PERSON

Complaints, payment questions, anything it is unsure of

Every draft is approved by the Membership team before it goes out, and every action is logged on the record.

See what we build for associations nonprofits

AFTER LAUNCH

The team that builds it can support it.

If you choose ongoing support, the people who wrote your manual answer your requests. Nothing is lost between building and running: requests are acknowledged the moment they arrive and picked up the same business day, and every change goes on the same release record.

About Support

LATER

Ready for AI when you are.

AI needs one clean record, agreed definitions and known owners. We design those in from the first sprint, so AI can be added safely later: small, with a person reviewing every draft.

Practical AI

The mechanics

The sprints are the easy part.

Short sprints with a working demo at the end of each are what any good partner should offer. Ours run like this.

Each requirement becomes a short specification your named approver signs before we build it
Every sprint ends with a demo in your Salesforce, not slides
Your staff test with scripts we prepare, and each team is trained on its part
A supported go-live, then the handover check

Sprint board · Lakeview Association

Sprint 3 of 4

Against the register

R-001Members, renewals and chapters on one recordDemo approved, Sprint 1Released

R-004Email preferences in one placeDemo approved, Sprint 2Released

R-005Payments and refunds that reconcileSpecification signed by Finance DirectorIn build

R-007Monthly report produced in a daySpecification with your approverNext sprint

Sprint 3 demo: payments and refunds, live in SalesforceThursday

How a build is charged

One rate. Every hour accounted for. Stop when you choose.

You pay for the time the build takes, reported against the requirements it was spent on. We talk through the numbers on a call, before you commit to anything.

1
One blended rate.
Architect, developer and project lead all bill at the same rate. Who does the work never changes what you pay.
2
Every hour accounted for.
Hours are logged against the numbered requirement they were spent on, so you see where the time goes as it goes, not on the invoice.
3
You can stop at any time.
Everything is documented as it is built, so what has been delivered is usable and yours, with or without us.

Hours by requirement · Lakeview Association · after Sprint 2

1RATEOne blended rateArchitectDeveloperProject lead

RequirementStatus0 h30 h60 hLogged 2

R-001Members and chaptersReleased48 h

R-002Gifts and soft creditsReleased29 h

R-003Event registrationsReleased21 h

R-004Email preferencesReleased14 h

3If you stop here, R-001 to R-004 are released, documented and yours

R-005Payments that reconcileNextNot started

R-006CE credits on the recordLaterNot started

So far112 hlogged across four released requirements

What you keep if you stop: Read: Owning your systems after the build

Where to start

With a Blueprint, or without one.

IF YOU HAVE A BLUEPRINT

The register is already written.

Every requirement is numbered, with the person who raised it and a priority set by your own leadership, so we go straight to specification.

About the Blueprint

IF YOU DON'T

Clear scope, or not yet.

If you already know exactly what you need, one or two conversations produce the register and a proposal. If the scope is still murky, we suggest starting with a Blueprint, four to six weeks of discovery, so the build starts from your needs.

Talk it through

“Kloudserv stands out as a company that is very genuine in solving for our needs and not just working to close the deal on the contract.”

Juan Calixto, VP of External Relations, Chicago Community Loan Fund

Questions

About owning what we build.

How do you make sure we can still run it in three years?

Four habits, on every build. Every feature traces to a numbered requirement and the person who raised it. Standard Salesforce comes before anything custom. A plain-English system manual and a release record are deliverables, not extras. And two of your admins run the real tasks before we call it done.

What if we need something Salesforce doesn't do as standard?

Then we build it, and say why. We first check whether standard Salesforce already covers the need, because custom work is where long-term cost and risk hide. When custom is the right answer, the reason, the approver and how it works go into the manual.

What is in the system manual, and who is it for?

It is written for the people who run the system, not for developers. For each automation, report and key setting it says what it does, why it exists, which requirement it came from and who approved it, plus how to change it where your admins can. It is yours.

What happens when someone has a new idea halfway through?

Good, it gets a number. Every new need comes through one door: a numbered change request with the hours and any effect on dates, and your named approver decides. Deferred ideas stay on the register as deferred, not lost.

What does the handover actually involve?

You name two admins. Before go-live is called done, they run the real tasks themselves: adding a chapter, changing a grace period, processing a refund, running a funder report. Anything they stumble on is fixed in the system or in the manual.

Which parts of Salesforce do you build on?

Whichever fit your needs. Our home ground is associations (members, renewals, events, certification and CE credits, chapters) and nonprofits (donors, gifts, grants, programs, volunteers), and we always start from what Salesforce already offers as standard before building anything custom.

How is the cost set, and can we stop?

By the time the build takes, at one blended rate for everyone on the team. Hours are logged against the numbered requirement they were spent on, and we talk through the numbers on a call before you commit. You can stop at any time; what has been delivered is documented and yours.

Will we depend on you afterwards?

No. That is the point of the manual, the release record and the handover check. Some organizations ask us to keep looking after it with Support, and then the same team that built it answers your requests. That is a choice, not a requirement.

Build something you'll still own in three years.

A 30-minute conversation about what you need Salesforce to do, and the best way to start.

Book a conversation Start with a Blueprint

Not ready for a call? See an example Blueprint