A Form Is Not Just a Form:

Gravity Forms, Salesforce and the Architecture Behind Website Submissions

Forms look simple…. A user fills in a few fields, clicks submit, and the data goes somewhere.

For a long time, that was probably enough of a mental model. A form was a form. It collected data, sent an email, and maybe created a lead or case somewhere. But modern websites are no longer just brochureware with a few contact forms attached. They are part of a wider digital operating system. They connect to CRMs, marketing platforms, payment gateways, analytics tools, preference centres, automation platforms, reporting models and downstream business processes. That means a form is rarely just a form anymore.

It is a capture point in a much larger system, and when that form connects to Salesforce, the real question is often not: “Which form tool should we use?” It is: “Where should the intelligence of the system live?”

Start with the architecture principle

Before choosing Gravity Forms, FormAssembly, Web-to-Lead, Web-to-Case, a Salesforce add-on, webhooks, Screen Flow, OmniStudio or Lightning Web Components, it helps to agree the architecture principle. One of the most important questions is:

Should Salesforce receive transformed data, or should Salesforce transform the data it receives?

Those are very different models.

In the first model, the external system prepares Salesforce-ready data. The website, form tool or integration layer decides what Salesforce object should be updated, how the fields should map, what values should be transformed, and what record should be created or changed. That can be fast and direct, but it also spreads business logic across external systems. It works, but over time it can quietly create technical debt.

In the second model, the external system sends Salesforce a structured source submission. Salesforce then owns the interpretation, transformation, matching, validation and downstream processing. That usually requires a more deliberate intake pattern, but it keeps the core business logic closer to the system of record. It is the difference between connecting tools quickly and designing a system that can last.

This is where patterns like a Data Source Entry, staging object or controlled intake object become important. They allow external systems like Gravity Forms to submit a consistent payload without needing to own the Salesforce data model or all of the downstream business rules. In that model, Gravity Forms does not need to know everything about Salesforce. It needs to capture the submission, package it correctly, and send it to the agreed intake point. Salesforce then decides what happens next.

That changes the conversation. The question is not simply: “Can Gravity Forms map to Salesforce?” It can. The better question is:

“Do we want Gravity Forms to map directly to Salesforce records, or do we want Gravity Forms to submit structured data for Salesforce to process?”

If the principle is that Salesforce owns transformation from any data source, then a controlled payload or webhook pattern may be the right answer. If the principle is that each source system sends already-transformed Salesforce-ready data, then direct field mapping becomes more attractive, but the governance needs to sit closer to the website. The principle should come before the tool choice.

The tool choice is only one layer

This is why form platform comparisons can get messy.

Gravity Forms versus FormAssembly sounds like a simple product decision. Gravity Forms versus a Salesforce-native form sounds like a technical decision. Webhooks versus a Salesforce add-on sounds like an implementation decision. But each option changes more than the form.

It changes who owns the data logic, who can safely make changes, where testing needs to happen, and how much governance is required before a form can go live.

Gravity Forms is a useful example because it can support several patterns. It can work with simple Salesforce capture, direct mapped integration, webhook-based submission, temporary storage, permanent storage, or very little long-term storage in WordPress. That flexibility is valuable, but it also means “we use Gravity Forms” is not really the architecture.

It could mean the website owns the field mapping. It could mean Salesforce owns the processing. It could mean a hybrid model where simple forms are easier to self-manage and governed forms follow a more controlled pathway. So the tool is only the visible part of the decision.

Capture and processing are not the same thing

A website form is often the right place to create the user experience. It can ask campaign-specific questions, capture UTMs, apply conditional display logic, change confirmation behaviour, and help marketing teams move quickly. But that does not automatically mean the website should decide how to match a person in Salesforce, how to prevent duplicates, how to apply consent rules, how to transform values, or how to trigger downstream processes. Those decisions may belong somewhere else.

In many Salesforce environments, the website should act as the capture layer. It collects the submission and passes it on in a structured way. Salesforce, or an agreed integration layer, then acts as the processing layer and decides what the submission means. That distinction is important because it changes the operating model.

If the website owns too much logic, it can be faster to change but harder to govern. If Salesforce owns more of the logic, the system can be more controlled and consistent, but some changes may need more formal support, testing and governance.

Neither model is automatically right or wrong. The point is to make the choice deliberately.

The real trade-off is agility versus governance

Direct field mapping can be a good fit for simple, low-risk forms: newsletter sign-ups, basic enquiries, simple lead capture, or lightweight campaign forms.

In those scenarios, it may be reasonable for a form administrator to map a website field directly to a Salesforce field. The benefit is speed. Marketing and digital teams can create forms, add fields, update labels, adjust confirmation messages and test campaign ideas without turning every change into a development task. That agility matters.

But the picture changes when a form affects more important parts of the system.

If a form touches consent, preferences, identity matching, duplicate management, campaign attribution, applications, payments, supporter records, student records or downstream operational workflows, direct field mapping may not be enough. In those cases, a controlled webhook, middleware or staging pattern can be stronger. The website captures the submission, but Salesforce owns the matching, deduplication, consent handling, validation, transformation and downstream processing.

The trade-off is that controlled processing is not always fully self-service. If a new field changes the payload, the staging model, the transformation logic or the downstream Salesforce process, then it may need technical support. That is not a failure of the form tool. It is usually a sign that the form is part of a governed business process.

The better question is not simply: “Can we add a field?” It is: “Can we add this field without accidentally changing consent behaviour, duplicate logic, reporting, automations, segmentation or downstream Salesforce processing?”

That is the question that decides whether the change should be self-service or governed.

Salesforce-native is not always the answer

It is tempting to assume that if Salesforce is the system of record, then Salesforce-native forms must always be the best answer.

Sometimes they are.

Salesforce-native experiences such as Screen Flow, OmniStudio or Lightning Web Components can be powerful choices for authenticated experiences, guided internal processes, complex applications, portal journeys or forms that need deep Salesforce logic at the point of interaction.

But they are not automatically better for every website form.

If the goal is to let a marketing team create campaign landing pages, test new messages, add lightweight questions, capture UTMs, adjust thank-you pages and respond to opportunities in market, a fully Salesforce-native form model may be too heavy.

It can move too much of the website experience into a Salesforce delivery process. That may protect governance, but it can reduce digital agility.

Gravity Forms can be useful because it keeps the website experience flexible while still allowing Salesforce to remain the system of record. That is often the practical middle ground: marketing gets a nimble capture layer, while Salesforce continues to govern the records and processes that matter.

This is showing up across projects

This is not a one-off issue.

Across different website and Salesforce projects, the same pattern keeps appearing. A discussion starts as a form tool decision, but quickly becomes a wider architecture and operating model decision.

On one project, the question may be whether a marketing team can create new forms and fields without external support. On another, the question may be whether the website should map directly into Salesforce objects, or whether Salesforce should receive a structured submission and own validation, matching, transformation and downstream processing.

They look like different problems, but they are really asking the same question: Where should the intelligence of the system live?

That question is becoming one of the most important design decisions in modern website and CRM integration work.

A simple way to frame the decision

A useful way to avoid over-simplifying the decision is to separate the form into layers.

Layer	Key question
Capture layer	How does the user submit the data?
Payload layer	What structured data is sent downstream?
Processing layer	Who transforms the submission into Salesforce records?
Governance layer	Who owns validation, consent, matching and dedupe?
Operating layer	Who can safely change forms and fields later?

Once those layers are clear, the options become easier to assess.

A team might choose Gravity Forms as the capture layer, a JSON payload as the hand-off, Salesforce as the processing and governance layer, and a hybrid operating model where simple forms are self-service but governed forms require support.

That is much clearer than simply saying: “We use Gravity Forms.” Because Gravity Forms is not one architecture.

It is a flexible form layer that can support several architectures.

The real decision

A form is not just a form.

It is a point where user experience, data quality, consent, identity, automation, reporting and operational process meet.

That is why form decisions should not be reduced to a simple tool comparison.

Gravity Forms versus FormAssembly is not the whole question.
Gravity Forms versus Salesforce-native forms is not the whole question.
Webhooks versus direct mapping is not the whole question.

The better question is: What should be easy to change, and what should be carefully governed?

Once that is clear, the form architecture becomes much easier to design.

Gravity Forms can be a strong choice when organisations need a flexible website capture layer that supports marketing agility. Salesforce-native forms can be the right choice when the process needs to live close to Salesforce. Webhooks, add-ons, staging objects and direct mappings are simply different ways to decide where the logic sits.

The goal is not to make every form self-service. The goal is to make the right forms self-service, and to govern the forms that need governance. That is the difference between choosing a form tool and designing a sustainable digital system.

The Enterprise CMS Trap

I recently read an article from WordPress VIP comparing WordPress with Adobe Experience Manager. It’s a good example of thought leadership in the CMS space and it prompted me to reflect on the platform conversations we have with clients every week.

https://wpvip.com/wordpress-vip-vs-adobe/

Platforms like Adobe Experience Manager are often positioned as the “enterprise standard”. On paper they offer powerful capabilities, content management, digital asset management, personalisation, and marketing integration. But those capabilities often come at a cost:

• High licensing costs
• Complex infrastructure requirements
• Long implementation timelines
• Heavy operational overhead

Many organisations end up spending enormous amounts of time and budget simply keeping the platform running, rather than improving their digital experience.

When the Numbers Don’t Add Up

This is where modern WordPress architecture often surprises people. With the right implementation partner, WordPress can deliver:

• enterprise-scale performance
• structured content models
• headless or hybrid architectures
• integration with marketing and CRM platforms
• flexible publishing workflows
• strong governance and security

All while remaining simpler to operate and simpler to evolve. That is why some of the world’s largest organisations run WordPress at scale.

Platform vs System

The platform itself is only part of the equation. What actually determines long-term success is the system built around it. A sustainable digital system includes:

• clear content architecture
• well-defined publishing patterns
• measurable page purpose
• strong analytics and insight
• integration with the wider technology ecosystem

Without that system thinking, even the most expensive platform will struggle to deliver value.

Bigger Doesn’t Mean Better

The comparison published by WordPress VIP between WordPress and Adobe Experience Manager is a good example of thought leadership in this space. WordPress VIP operates at a global scale, supporting some of the world’s largest digital publishers and organisations. Their platform provides managed infrastructure and tooling designed for extremely high-traffic environments.

But the principles they advocate are not unique to WordPress VIP. They are principles that experienced WordPress partners apply every day. At AlphaSys we approach digital platforms in much the same way. The scale may be different, but the thinking is the same.

The focus is not on the platform alone. It is on designing systems that are sustainable, flexible, and capable of evolving over time. That means thinking carefully about:

• how content is structured
• how publishing workflows operate
• how platforms integrate with CRM and marketing systems
• how insights and analytics inform improvement

When those elements are designed well, WordPress becomes a very powerful foundation.

The Real Question

So the question organisations should be asking is not:

“Which CMS is the most powerful?”

Instead, it should be:

“Which platform allows us to build the most sustainable digital system?”

In many cases, the answer is WordPress – when implemented well.

A Day in the Life of Digital Director

Most days start somewhere between 7:00 and 7:30am, depending on where I need to be that day.

The first thing I do is make a green tea and turn on Channel 7 news. It’s mostly background noise, but it gives me a quick sense of what’s happening in the world. While the news is on, I check overnight Teams messages and email. Working across teams and time zones means things often move while I’m asleep.

From there I open Feedly, which is where I keep a curated list of sources I follow. Over time I’ve organised them into folders that loosely mirror the things I care about and the work we do, things like: Branding & Design, Web Development, Tech, AI, Salesforce, Hosting, Membership and Fundraising, along with broader topics like News, Projects & Leadership, Health, Elearning, and Environment. There are also a few lighter folders like Lifehacker, Entertainment & Gaming, and one simply called FUN for memes and internet nonsense.

The goal isn’t to read everything – that would be impossible.

Instead I scan headlines and tag things as I go. Some articles get marked read later so I can properly digest them. Some get shared with team members if they’re relevant to the work they’re doing. Others get tagged simply because I know the topic will come up at some point and it’ll be useful to have something ready – I can’t read everything, but knowing I’ve seen something before and can find it again makes me feel prepared.

Once I’ve got a bit of context for the day ahead, I get ready and head out.

The Commute (or the Transition)

What happens next depends on where I’m working that day.

Some days I’m heading onsite, which means a drive. When that happens I usually open Headway and try to cram a book or two on the way. It’s a quick way to absorb ideas without needing hours to read. I’ll share the books that have stuck with me most in another article.

If I’m on the Metro, the time tends to look a bit different. That’s usually when I open up a conversation with AI and work through the bigger or messier situations, the ones that need thinking rather than reacting. Sometimes it’s about how to handle something in the team, sometimes it’s about strategy, and sometimes it turns into deep research on topics that matter to the growth of our business.

A lot of this time ends up being about personal and professional development, reflecting on how things are going, what could be done better, and what strategies might help the team and the business move forward. Part of me is always on a quest for learning and growth, so this time is genuinely energising. It’s also a small moment of self-care in the day, time to think, reset, and remind myself that the goal isn’t just to do more work, but to do better work and do work better.

If I’m working from home, the commute disappears. What I gain instead is a few extra minutes to breathe, settle in, and get a head start on the backlog before the day properly begins.

However it happens, that small transition between morning context and the workday is often where the first real thinking of the day happens.

The Workday

The day itself is usually a thick combination of meetings, backlog work, and interruptions.

Some interruptions are easy to deal with. Others completely reshape the day. A quick question can turn into a design discussion. A small issue can uncover something bigger. And sometimes something urgent lands that simply wasn’t part of the plan.

Part of my day is also spent quickly scanning our operational systems – forecasts, Harvest time logs, Salesforce opportunities, logs in client websites, partnership systems, and overnight system notices. It’s not something that takes hours, but it does require an experienced eye. Moving quickly through the data helps surface the things that are important or urgent, before they become bigger problems.

Every day we need to understand what we might have missed overnight and what needs to be dealt with in more real time. Doing that often uncovers a wealth of issues, each of which could easily consume the entire day if you let it. Each one needs a different response.

• Some need quick intervention.
• Some need delegation.
• Some just need a nudge to keep moving.
• And some need to be deprioritised.

The challenge is not getting stuck on a single issue.

Most days already have six or more hours of meetings scheduled, often back to back. Working from home has made calendars feel infinitely available. Some meetings I know about and have planned for. Others get slipped in without much conversation. And occasionally a client books time assuming I must be available.

All of those meetings need responses, planning, and preparation.

My calendar is usually a week or two out, and most of the available spaces are already earmarked for the work of that week. When something urgent appears, it usually means something else has to move further down the road – That’s just the reality of limited time.

I once read about East African runners using a term that sounded like korokruch – settling into a rhythm where pace, breathing and effort align. The point isn’t to sprint the whole run. It’s to find a sustainable cadence and hold it. I try to apply the same thinking to my week. Instead of reacting to everything immediately, I create rhythm in the calendar, regular spaces for certain conversations, decisions and reviews. When people know those moments exist, they can park non-urgent issues until then and raise them when I’m ready to receive them. It helps keep the week moving without everything becoming urgent.

A good day is about eight or nine hours of solid work, often with barely enough time to stop and breathe. If I’m lucky I’ll get a chance to buy or heat up lunch and eat it at my desk – And even then, there’s usually more waiting for tomorrow.

The Evening Switch

Most days I aim to finish around 6pm so I can flip the switch and spend time with family, Some days cooperate – Other days I pause around 7pm, knowing I’ll be back later.

My wife works a later shift and usually gets home around 7:30pm. We’ve recently started carb cycling, which means dinner is less spontaneous than it used to be. When I stop work it’s usually straight into the kitchen, cooking dinner and often preparing the next day’s lunch at the same time.

When she gets home we eat together, usually with a glass of wine, and take a moment to decompress.

The Quiet Hours

After dinner, while my wife settles in to relax in front of the TV, I often head back to work.

On the good days, this is the best part of the day. It’s when I get time to think, planning, writing down points of view, researching ideas, or working on development projects we’ve been wanting to explore – On the bad days, it’s simply catching up on work that never quite finished earlier … Sometimes those days feel like they never really end.

Switching Off

When we can, we wind down together with a sitcom, drama or reality show, before inevitably flicking over to YouTube Shorts for a few minutes. My algorithm is mostly tuned for laughs, which is probably exactly what I need at that point in the day. Before bed I do one last sweep of messages and notifications, just to make sure nothing urgent has been missed.

Then it’s time to reset and start again tomorrow.

Wrapping Up

I know that all sounds like a lot, and sometimes it is. But I get to do work I genuinely enjoy, with organisations that truly deserve it and appreciate it. At AlphaSys, we focus on for-purpose organisations, and the impact they make is critical to the world we live in. I can’t do what they do. But I can make it easier for them to do it – and to do it better.

A website is not something you launch and forget. Like any system that serves real people, it needs regular maintenance. Not technical maintenance like plugin updates or backups, but content and experience maintenance. Your analytics tools already contain the clues. If you know where to look, they will tell you:

• Which pages aren’t performing
• What people are trying to find but can’t
• Where users are hitting dead ends
• What links across your site are broken

Reviewing this data regularly is one of the simplest ways to improve your website. In our work, there are four reports we recommend reviewing every month.

1. Pages With 100% Bounce Rate

A page with a 100% bounce rate means every visitor left after viewing only that page. That doesn’t always mean the page is bad. But it does mean the page is not moving people anywhere else, and that is ok if that is the intent of the page. If you page is about content consumption and you have a high bounce rate and a good time on page, then the page probably did it job. However, most pages are not about consumption, typically pages are to either Convert, Inform, Engage, Guide or Bridge. When you find these pages, ask:

• Where should traffic to this page come from?
• Where should visitors go next?
• Is the page linked from the rest of the site?
• Is the call-to-action clear?
• Does the content match the visitor’s expectation?

Sometimes the fix is simple:

• Add links to related content
• Add a clear call-to-action
• Improve navigation to or from the page

Sometimes it reveals a deeper issue: the page exists, but it has no real role in the site. Every page should have a purpose.

2. Pages With No Time on Page

Pages where visitors spend less than a few seconds often indicate one of three problems:

1. The page didn’t match what the visitor expected
2. The content is confusing or poorly structured
3. The visitor landed there by mistake

Filtering these pages helps identify:

• Pages that should not be indexed
• Pages that need better internal linking
• Pages that need clearer content structure

Often the problem is not the content itself, but how the page is reached.

3. Unsuccessful Searches

Site search is one of the most powerful insights you can collect. When someone uses search, they are telling you exactly what they want. But sometimes the search produces no results. That’s valuable information. Look at these searches and ask:

• Should this content exist? If users are repeatedly searching for something that doesn’t exist, it may indicate a gap in your site.
• Is it a spelling mistake? Common misspellings can easily be handled by adding synonyms or spelling variations in your search engine.

Tools like Relevanssi make this very easy.

Is the content there but hard to find? If the page already exists, users may simply be using a different word for it. Adding synonyms can often solve this. Search data is one of the fastest ways to understand how users think about your content.

4. 404 Errors

Broken URLs happen on every website. Links change. Pages are removed. External sites link incorrectly. The key is not avoiding 404 errors entirely – the key is managing them properly. We recommend using a redirect tracking tool so you can group and analyse 404 requests. Then review the largest groups.

• Does the page exist somewhere else? If so, add a redirect.
• Should the page exist? If people are repeatedly requesting a page that doesn’t exist, it may indicate missing content. Creating the page may be the right solution.
• Is the traffic suspicious? Many 404 requests come from bots scanning your site. If the requests are clearly malicious or irrelevant, you can simply exclude them from tracking.

Once the main issues are addressed, clear the logs and start fresh for the next review cycle.

5. Broken Links

The final report to review regularly is broken links within your site. Broken links create frustration and damage trust. Fixing them is usually straightforward:

• Update the link to the correct page
• Redirect the missing page
• Remove the link if the content no longer exists

Most sites accumulate broken links over time. The important thing is to clear the backlog regularly so the list stays manageable.

A Simple Monthly Website Maintenance Routine

You don’t need complex tools or hours of analysis. Once a month, review:

1. Pages with 100% bounce
2. Pages with very low time on page
3. Unsuccessful searches
4. 404 errors
5. Broken links

Each report highlights a different type of problem.

Taken together, they reveal where your site is:

• confusing users
• hiding useful content
• sending visitors to dead ends

Fixing these issues regularly keeps your site healthy and ensures the content you’ve already created continues to perform.

A Website Is Never Finished

The best websites are not built once. They are continuously improved. Your analytics tools already contain the signals that tell you what to fix next. All you need to do is look.

Long has the web world been dominated by SEO (Search engine optimisation) for public visibility, but with the rapid evolution of AI LLMs and search engines such as Perplexity, the question becomes, how does my site remain relevant when it’s no longer the user selecting a link, but an AI that decides the best information to display?

As the traditional rules of SEO no longer guarantee visibility. New methods are required to direct AI towards our websites. Which leads us to the question of what an AI looks for when choosing what information to display?

When you ask ChatGPT about the best restaurants in the Sutherland Shire, it will first suggest going to a better location. After that, it scrapes websites related to the search query and decides which content to display based on multiple factors, including metadata, content quality, trust signals, and formatting. Understanding these factors is key to what we’re calling GEO (Generative Engine Optimisation).

On-Site Optimisation Techniques

1. Write for Humans, Optimise for AI

Companies are designing AI to appear as humans, which includes the way they are designed to gather and display content. AI is far more likely to select short paragraphs/sentences using direct language over a large wall of text. AI models reward quality, not quantity.

Best practices:

• Use natural language that directly answers questions
• Put the most important information first
• Break complex ideas into smaller chunks
• Avoid jargon unless it relates to your audience

2. Content Structure

AI models arrange website content into structures. If your website’s structure isn’t ideal for AI to process, it will simply skip over it. Building pages with AI-friendly formatting is essential for your website to be seen.

Best practices:

• Descriptive headings that explicitly state what the section covers
• Short paragraphs with a single idea each (2-4 sentences maximum)
• Bullet points and numbered lists that neatly outline steps, features, or concepts
• Logical information flow: Question → Explanation → Example → Conclusion
• Consistent formatting throughout the page
• Tables and structured data for comparisons, specifications, or data sets

3. HTML and Schema

Now we enter the fun technical part. AI systems rely heavily on structured data to understand context and relationships between information.

Best practices:

• Use HTML5 semantic elements (<article>, <section>, <aside>, etc.)
• Implement schema markup (Organisation, Article, FAQPage, Product, Review, etc.)
• Add an FAQ section for common questions, which directly feeds AI responses
• Use breadcrumb markup to show site hierarchy

4. Using Metadata

Metadata tags help the AI understand your content’s purpose

Best practices:

• Write clear, descriptive title tags that match user intent
• Craft meta descriptions that summarise content accurately
• Use descriptive alt text for images (AI uses this to understand visual content)
• Include “Last updated” timestamps prominently on pages

5. Create Answer-Focused Content

AI models prioritise content that directly answers specific questions. This means moving beyond keyword stuffing to genuine question-and-answer formats.

Best practices:

• Create dedicated FAQ sections addressing common queries
• Use question-based headings (e.g., “What is GEO?” instead of “GEO Definition”)
• Provide concise answers in the first 1-2 sentences, then elaborate
• Include real examples and case studies
• Add comparison content (X vs. Y articles)

Off-Site Optimisation Techniques

1. Cultivate Brand Mentions and Citations

The more that your website is mentioned on other websites, the more AI will trust you.

Best practices:

• Ensure consistent NAP (Name, Address, Phone) across all platforms
• Get mentioned in industry publications, podcasts, and forums
• Encourage brand mentions through PR
• Monitor brand mentions using tools like Google Alerts

2. Leverage Third-Party Review Platforms

AI systems review third-party platforms and websites to assess trustworthiness and quality.

Best practices:

• Actively manage your Google Business Profile and collect reviews
• Maintain profiles on industry-specific review sites such as Trustpilot
• Respond professionally to all reviews, both positive and negative
• Showcase reviews and testimonials on your website
• Monitor your overall review ratings across platforms

3. Establish Authority Across the Web

AI models recognise when a brand or author is consistently referenced as an authority on specific topics.

Best practices:

• Publish consistently on the same core topics
• Contribute to industry publications
• Speak at conferences and events (which generate mentions)
• Participate in professional communities and forums
• Build author profiles with E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals

Salesforce Integration by Design

…not as an after thought

Most Salesforce–WordPress integrations are treated as a bolt-on. A plugin here, a connector there, some custom scripts to glue it all together — and suddenly the “integration” becomes the riskiest, most unpredictable part of the project.

Our approach is different.

• We don’t treat integration as a feature.
• We treat it as architecture.

Our platform is designed with the assumption that Salesforce will be a critical part of the ecosystem. That means the plumbing is already built, the patterns are already defined, and the technology is already in place. Instead of patching systems together later, we make Salesforce integration feel native to the way the website works.

Our approach is powered by three core capabilities.

Integration is Configuration, Not Engineering

Most organisations end up spending more on integration than they ever expected — not because Salesforce is difficult, but because the website was never built with Salesforce in mind. – We flipped that model. We have invested a little more in the core architecture, so integration doesn’t become the unpredictable, expensive part of the project later.

When the foundations assume Salesforce from the start:

• Object sync is already part of the system
• Web-to-Lead and Web-to-Case slot straight into Gravity Forms
• Campaign, consent, and subscription updates have a clear path
• Matching and upsert logic stays entirely native to Salesforce
• And teams aren’t forced into custom connectors or workaround logic

The core build may be slightly higher, but the integration effort is dramatically lower because we’re configuring rather than engineering. It stays predictable, consistent, and repeatable as your needs evolve, making this simply a better way to work. Invest once in the right architecture, and avoid the hidden costs later.

Tech Stats Every Nonprofit Organisation Needs to Know in 2026 

What new research findings tell us – and how your team can take action. 

For Australia’s nonprofit sector, 2026 is shaping up to be a decisive year for digital systems in nonprofits. 

As service demand grows and funding stays tight, leaders face a choice. Stick with what’s barely working or invest in tech that supports growing caseloads and workload, without making admin harder. 

The Digital Technology in the Not-for-Profit Sector Report published by Infoxchange, highlights significant gaps in cyber security, data quality, workforce capability, and the sector’s gaps in budget, skills, and systems that prevent adoption of new tech. 

At AlphaSys, we work with for-purpose orgs to fix broken systems, upgrade old platforms, and train teams properly. We help build systems that are easy to run, even as your needs shift. Technology should not become a barrier. It must serve and enable the mission. 

As every for-purpose leader knows, there’s real potential to deliver stronger outcomes at scale, as we’ll explore in the sections below. These insights from the Infoxchange report reflect where many nonprofits are today – and what’s holding them back. 

1. Cyber security vulnerabilities persist 

🔐 60% of nonprofits still do not enable multi-factor authentication (MFA)

Cyber threats are becoming more sophisticated. Yet many are still vulnerable to basic breaches, with MFA underutilised by 60%. 

Legacy systems often lack basic modern cyber security features. Work is often done in silos which lack rigorous credential checks, clear permission structures, or shared accounts that leave trails for record keeping. 

Why it matters: 

A breach doesn’t just put donor and client data at risk. It can damage your organisation’s reputation and divert limited resources away from service delivery. 

What to do:

Choose systems that are secure by design. At AlphaSys, we work with platforms that have built-in protections like multi-factor authentication, role-based access controls, and clear audit trails. When security is built in from the start, it’s easier to manage. Salesforce Nonprofit Cloud is one example. 

2. Budget constraints remain the biggest barrier to transformation 

💸 61% of groups say budget constraints are their #1 challenge 

Stagnation is most often attributed to budget in nearly all sectors, and in a paradox, is often solved by the same technology that reduces administrative workload, automates reporting, or shrinks expenditure by automating a myriad of processes. 

Why it matters: 

Delaying digital upgrades often leads to bigger costs later. Outdated systems don’t connect, get expensive to patch, and can’t keep up with needs. Rebuilding from scratch then becomes unavoidable and costly. 

What to do:

Look at the whole system, not just one broken part. Instead of one-off fixes, design systems that stay useful, stable, and cost-effective over time. Build for long-term value, not quick wins. 

3. Data quality is limiting impact and decision-making  

📉 Only 25% of organisations report their data is adequate for reporting and analytics. 

Many find it challenging to progress beyond basic data collection. Dominated by siloed systems, piecemeal manual workflows, and rampant excel spreadsheet or legacy case management systems usage. 

The result? Limited visibility and slower reporting. Reporting takes tedious time to compile and becomes increasingly untrustworthy, and strategy is designed more on gut feel instead of reliable data. 

Why it matters: 

If you can’t measure your impact, how can you improve it? How can you share your story with funders? How can you better support your clients? 

What to do:

To improve data quality, nonprofits must invest in integrated systems that centralise data, automate reporting, and surface insights. With the Salesforce Nonprofit Cloud and a smart implementation approach, we enable clients with systems that use data to guide decisions and show results.

4. Workforce capability is lagging behind tech   

👥 Only 23% say staff are confident with the digital tools available to them for everyday tasks.  

Digital transformation doesn’t end with go-live. The launch of a system is just one step in a longer rollout. Systems are often underutilised or misused when staff are not properly trained, supported, or bought into the system. 

The ability to adapt to internal changes and build capability has become increasingly important due to role changes, turnover, and tech fatigue.

Why it matters: 

Without capable users, even the best systems fall short. When staff aren’t confident, you lose time, miss insights, and risk burnout. 

What to do:

We train staff in ways that stick. Co-designed tools work because people use them. Processes are co-designed with end users which enable leadership teams to drive adoption, so change sticks across your team, not just your tech.

5. AI is changing work – but practical use in nonprofits is still low    

🤖 Fewer than 20% use AI tools regularly. 

Many sectors now use ChatGPT, Copilot, and Gemini in their daily workflows, but for most nonprofits, these tools tend to be more theoretical than practical. 

Slow adoption can be attributed to low awareness, technical uncertainty, and ethical concerns like data privacy, bias, and accountability. 

Why it matters: 

AI is not simply about streamlining processes. The primary focus is to eliminate tedious tasks so people spend less time on admin and more time engaging clients, solving problems, and driving your mission forward. 

What to do:

Choose platforms that can accommodate AI even if you do not plan on using AI anytime soon. We help simplify systems now, so AI can fit in when you’re ready. 

Your systems should enable your mission, not constrain it. 

These stats tell a story: Australian orgs aspire to achieve more, however, still struggle because of obsolete systems, insufficiently utilised data, overextended staff, and stretched teams. 

At AlphaSys, we believe technology should make your job easier – not get in the way. We focus on building sustainable systems for social good, systems that: 

• Withstand and build security and trust 

• Streamline operational demands 

• Facilitate active decision making and data-informed choices  

• Support your staff on every level 

Whether you need a full rebuild or a few smart upgrades, we build systems that last and support you as you grow. 

Custom vs Point Solutions: Do You Really Have to Choose?  

Do you invest in a custom-built enterprise system designed for scale? Or patch together a mix of point solutions to meet your immediate needs? 

Choosing the right technology for your nonprofit organisation can feel like a high-stakes either/or decision.

On one hand, there is the custom enterprise solution: robust, scalable, and often tailored to large, complex operations. On the other, the point solutions approach: practical, cost-effective tools designed to meet specific needs quickly.

But here is the good news: modern nonprofit technology no longer forces you to choose between the two extremes.

At AlphaSys, we work with Australian for-purpose organisations that want the best of both worlds: systems that are powerful enough to scale, but flexible enough to meet them where they are today. Because we operate in the Australian context every day, we understand the realities of local funding models, compliance obligations and service delivery across states and territories.

In this blog, we explore what the custom vs point solutions debate looks like in 2025, and why platforms like Salesforce Nonprofit Cloud are helping teams move beyond the binary.

What’s the difference between custom and point solutions?

Custom enterprise systems are comprehensive platforms that unify operations like fundraising, program delivery, HR, and finance into one centralised system. These systems are ideal for organisations with a long-term, strategic view of digital transformation.

But custom systems come with trade-offs. They can be expensive, slow to implement, and may require specialist support. If your team lacks internal technical capability, these platforms can quickly become difficult to manage.

Point solutions, on the other hand, are designed to solve specific problems. Email marketing, donor databases, payment tools, and event platforms are common examples. These are quick to roll out, relatively low-cost, and effective for small teams focused on a single issue.

The challenge is that as your organisation grows, point solutions can become limiting. Data gets siloed. Staff juggle multiple systems. Reporting becomes tedious. And strategic oversight is harder to achieve.

Why the old approach is no longer enough

Most Australian nonprofits today sit somewhere in between. Your organisation might be using spreadsheets for volunteer rosters, a basic CRM for donors, and a standalone case management tool that does not integrate with anything else.

This patchwork approach may have worked when your operations were simpler. But as services expand and expectations increase, your systems need to be able to:

• Scale without constant rework
• Centralise your data and reporting
• Support compliance and security
• Integrate your existing tools
• Adapt to changing needs

In Australia, that also means keeping pace with evolving privacy expectations, NDIS and government reporting requirements, and funding contracts that demand clearer evidence of impact.

Relying on outdated, disconnected technology can create more friction than it solves. This is why many nonprofits are now turning to hybrid systems that offer flexibility without fragmentation.

How Salesforce Nonprofit Cloud offers both flexibility and scale

Salesforce Nonprofit Cloud gives you the benefits of a product-based system, with the flexibility of a platform. It helps nonprofits avoid the classic trade-offs between speed and stability, or simplicity and scale.

It offers:

• Modular capability, so you can start with core functions like fundraising or service delivery and add more over time
• Pre-built functionality, for faster setup and lower complexity
• Platform-level integration, bringing all your point tools into one ecosystem
• Strong governance, including multi-factor authentication, role-based access, and audit trails
• Continuous innovation, supported by Salesforce’s product roadmap and ecosystem

For Australian nonprofits, this means you can begin with the areas that matter most, whether that is managing donors, clients, volunteers or grants, and grow into a broader, integrated platform as your needs and funding allow. Salesforce supports both long-term digital transformation and incremental growth. It is not locked into one way of working, and it can grow with your organisation at your pace.

How AlphaSys makes it work for you

At AlphaSys, we understand that no two nonprofits operate in exactly the same way, especially within the diversity of the Australian sector. Regional service providers, national charities, peak bodies and NDIS-funded organisations all face different pressures and regulatory settings.

That is why we do not just build systems; we co-design them with you.

We often begin with a real, immediate challenge: disconnected teams, inefficient processes, or gaps in visibility. From there, we build a roadmap that balances:

• Strategic foresight, so your systems are future-ready
• Human-centred design, so the tools support your people, not the other way around
• Ongoing support, so you are never left stuck after go-live
• Adaptable growth, so new features can be added when you are ready

Because we work day in, day out with Australian for-purpose organisations, we design with your context in mind, including government funding cycles, NDIS and program reporting, local data residency expectations, and the realities of stretched teams.

You do not have to choose between usability and scalability, or between a fast rollout and a long-term plan. We help you get both, with systems that are built for purpose and built to last.

Key questions to ask when choosing your next system

Before committing to a tech path, ask yourself:

• Is your current system limiting your ability to track outcomes, collaborate, or serve clients?
• Are your teams dealing with manual workarounds or duplicated data?
• Are you locked into tools that cannot scale or integrate easily?
• Do you have the internal resources to maintain a complex system? Or would shared support help?
• Do your systems reflect Australian regulatory, funding and reporting requirements, or are you constantly working around them?

If these questions sound familiar, it might be time to rethink your tech choices.

Final thoughts

The smartest choice is the one that’s built for your organisation.

You do not have to choose between going all in on custom enterprise software or stitching together a series of disconnected tools. And you certainly do not have to compromise on functionality, flexibility, or your mission.

With the right platform and a trusted partner, you can build a system that is:

• Designed around people, not just processes

• Flexible enough to meet your team where it is

• Scalable enough to grow with your impact

• Grounded in the Australian nonprofit context

• Supported by an ecosystem that is always improving

Why We Build on Cloudflare

(and Why Last Night Proved Exactly Why We Do)

If you noticed a ripple across parts of the internet overnight, you weren’t alone. A brief Cloudflare disruption made headlines around the world as major platforms, from social networks to AI tools, all reported intermittent issues. Outages like this always spark a noise from online commentary (and a fair share of memes), but for us, the incident is also an opportunity to talk openly about the architecture choices we make for every site we build and manage.

And importantly: why last night actually reinforces our confidence in those decisions.

Cloudflare: The Internet’s Backbone

Cloudflare powers an enormous portion of the modern internet – around 20% of all websites! This including many of the world’s most recognisable brands. Its global edge network handles billions of requests every day, accelerating performance, blocking attacks, and ensuring websites stay fast and secure no matter where visitors come from.

When you see a company operating at that scale, serving that much of the world’s traffic, a momentary disruption isn’t a sign of fragility – it’s proof of the complexity and sophistication involved in keeping the internet running.

And importantly:
Cloudflare resolved last night’s issue quickly, transparently, and with the kind of stability you only see from a mature, deeply battle-tested platform.

How We Use Cloudflare (Twice)

We rely on Cloudflare in two key ways across the sites we manage:

1. We use Cloudflare directly

This gives us control over DNS, edge caching, performance optimisation, and security layers such as WAF, bot protection, and rate limiting.

2. WP Engine uses Cloudflare under the hood

Because our hosting partner WP Engine integrates Cloudflare’s technologies deep into their platform, our sites effectively get double the benefit:

• Global caching and acceleration
• Intelligent traffic routing
• Layered security
• Redundant network paths
• Automated protection against DDoS and malicious traffic

Even during last night’s disruption, this layered approach ensured that several sites experienced minimal (or no) impact.

A Reminder: All Technology Carries Risk. The Question Is How You Mitigate It?

No technology platform, no matter how large or sophisticated, can guarantee 100% uptime forever. Google goes down. AWS goes down. Microsoft goes down. Apple services go down. And yes, Cloudflare can experience an issues too.

What matters isn’t the existence of risk, but the quality of the platform’s response:

• Was it detected quickly?
• Was it communicated clearly?
• Was the fix implemented fast?
• Was the root cause transparent?
• Did systems recover gracefully?

With Cloudflare, the answer to all of the above was a resounding yes.

Why We Continue to Recommend and Trust Cloudflare

Last night gave the world a rare visible reminder that Cloudflare sits at the core of how the internet works. But it also highlighted why we continue to trust the platform as the foundation for our clients’ digital presence:

• Unmatched global reach
• Best-in-class security
• Performance that is difficult to replicate elsewhere
• Fast, transparent incident response
• A long-term track record of reliability

If anything, the brief outage was a reminder of just how rare disruptions are for a platform of this scale – and how resilient the ecosystem around it has become.

Our Commitment to Stability

We design our hosting and infrastructure strategy with layered resilience in mind. Using Cloudflare directly, and then again through WP Engine, gives our sites multiple protective and performance layers. It’s part of our ongoing commitment to delivering:

• Fast websites
• Secure environments
• Reliable uptime
• Predictable performance
• Modern infrastructure with best-in-class partners

Incidents like this one simply reinforce why these choices matter.

If You Want This Level of Confidence in Your Digital Infrastructure

We’re monitoring all services and reviewing logs across every site under our care. If you want a breakdown of how your site behaved during last night’s event—or if you’d like to understand more about how our Cloudflare-powered architecture protects your digital presence—we’re here to help.

How We help Nonprofits Grow: The AlphaSys Game Plan in 4 Steps  

Whether you’re running a large national program or a small community service, these four steps form the foundation of how we support long-term impact. 

At AlphaSys, we believe technology should support your mission, not get in the way. But many Nonprofits are held back by outdated systems, scattered data, and limited support. 

That’s why we developed the AlphaSys Gameplan – a clear, step-by-step approach to building systems that help organisations grow in a sustainable and manageable way. 

This gameplan is a broad view of our initial approach. In practice, every solution we deliver is shaped to fit each organisation’s unique goals, context, and community. 

Why this matters 

Technology can help teams achieve impact, but only when it’s aligned with purpose. 

According to Infoxchange’s 2024 Digital Technology in the Not-for-Profit Sector report, only 23% of organisations say their data helps them measure impact in a meaningful way. Without that insight, it becomes harder to plan, report, and make informed decisions. 

Our approach tackles this challenge head-on. We empower teams to go from reacting to problems to planning and executing with confidence. 

Step 1: Understanding with empathy 

We start by listening to your story to see the full picture.  

This step is not just a tech audit. It’s about getting a good grasp of your mission, your team, the challenges you face, and what success looks like for you and the communities you serve. 

Questions we explore include: 

• What does growth look like for you? 

• Where are your current processes falling short? 

• What stories do you want your data to tell? 

This helps us identify not just what to fix, but what to build, so your technology supports your strategy, not the other way around. 

Step 2: Defining success together 

Next, we move into co-design. 

We bring key stakeholders and end users from the start, so the system we build with Salesforce reflects real needs and fits everyday workflows. 

This lays the groundwork for us to build solutions with Salesforce that are not just technically sound, but also user-friendly, future-ready, and grounded in your day-to-day reality. 

We map stakeholder journeys, prototype user flows, and test with your team. A system only works if your team finds it useful and easy to use. 

And because change is never just about technology, we also start preparing your people for what’s ahead. That way, when the new system arrives, your team is already engaged, supported, and ready to make the most of it. 

Step 3: Guiding your team through change 

Technology projects succeed or fail based on people, not just systems. This step is about preparing your team for what lies ahead, giving them clarity, confidence, and ownership of the change. 

We focus on change management as much as delivery: 

• Setting clear expectations for timelines, roles, and responsibilities 

• Building buy-in from leadership and frontline staff 

• Identifying champions within your organisation who can guide others through the transition 

• Communicating the “why” behind the changes so everyone understands the purpose and impact 

• We also look at training needs, communication rhythms, and practical ways to minimise disruption to your daily work. 

It is not about overwhelming your team with detail. It is about making sure people feel equipped, supported, and ready to embrace new ways of working. 

When people are prepared, the technology becomes easier to adopt, and the change feels less like a hurdle and more like a natural step forward. 

Step 4: Actively serving clients 

Our support doesn’t end when  the system goes live. 

We stay actively involved, providing ongoing support that adapts as your organisation changes. 

We help teams review progress, adjust strategies, and keep your systems aligned with your mission as it evolves. We help govern your solutions, making sure they remain aligned with your goals and compliance needs. 

Nonprofit work rarely stays the same for long. Funding cycles shift, programs evolve, community needs change. Your technology must adapt alongside these dynamics – not just sit on the sidelines. 

• Monthly conversations are where the detail lives. We meet to plan upcoming work, review progress, and quickly solve any issues. This rhythm keeps your systems nimble and responsive.  

It’s about maintaining momentum without overloading your team, catching problems before they grow, and making sure your tech remains a practical tool, not a burden. 

• Quarterly conversations allow us to step back to assess bigger questions. Are your organisation’s priorities still on track? Have your guiding principles or strategic focus shifted? This is the moment to check if the system you have supports your current reality or if adjustments are needed.  

It’s not just a status update but a chance to pause and ensure technology continues to reflect your evolving mission and impact goals. If misalignments emerge, we revisit success definitions together, realigning technology to what matters most now. 

• Yearly conversations dig even deeper. We explore whether your organisation’s core fundamentals have changed. Examples of these would be leadership shifts, new service models, compliance requirements, or community expectations.  

It’s a full reset point to confirm we still understand your mission, challenges, and how your systems can best support you. If fundamentals shift, we return to listening with empathy, rebuilding the foundation for your technology strategy. 

Together, these conversations create a living, adaptive partnership. They ensure your technology investment isn’t a one-off project but an ongoing asset that grows with you over time, through every program change, funding shift, or growth spurt. 

Why Salesforce? 

For many non-profits, choosing a technology platform is about more than just IT – it’s about finding tools that help them work smarter and stay focused on their mission. 

Salesforce is widely used across the non-profit sector, both globally and here in Australia. Well-known organisations like Anglicare Sydney, The Smith Family, and Beyond Blue use it to manage their programs, track data, and stay connected with the people they support. 

Based on what we’ve seen across the sector, we believe Salesforce could be a strong fit for your organisation too – especially if you’re looking for a flexible, future-ready solution. 

Here’s why: 

Flexible and scalable 
Salesforce works for organisations of all sizes. Whether you’re a small team or a large provider, you can start with what you need and add more as you grow. 

Designed to support outcomes 
Salesforce offers tools for case management, program tracking, volunteer coordination, fundraising, and more. It helps teams stay focused on delivering impact, not just managing systems. 

Reliable data in one place 
With Salesforce, your data is centralised. That makes it easier to track what’s happening across services, make informed decisions, and report on your work with confidence. 

A strong community 
Salesforce has a well-established presence in Australia. There’s a local support network, active partners, and a global nonprofit community sharing tools, ideas, and lessons. 

Constant improvement 
Salesforce is more than just a CRM. It’s a platform that continues to evolve, with built-in AI, automation, and integration options to help you work more efficiently. 

With AlphaSys as your implementation partner, you don’t need to figure it all out on your own. We help you make the most of it, every step of the way. 

The AlphaSys difference 

We are not just a tech partner. We are mission-aligned collaborators. 

We work with purpose-driven sectors and understand the practical realities of nonprofit work – limited time, changing requirements, and complex reporting needs. 

We’re not just here to deliver a one-off project. We’re here to help you build something that works now and keeps working later.