Skuid, now sold as Nintex Apps for Salesforce, is a toolkit for building custom pages and apps on your Salesforce data with drag-and-drop components instead of code. Twopir Consulting has implemented Skuid on the Salesforce Platform: we work out where it fits your business use case, implement it with Salesforce, and train the people who will use it. One team from use case to an app your users actually adopt.
Trusted by 500+ organizations, from growing and mid-market companies to enterprise teams, to design and build the Salesforce applications their people use every day.
What We Implement
Skuid is a cloud-based, user-experience toolkit for rapidly creating and optimizing business applications across data repositories and services. With Skuid’s drag-and-drop App Composer, anyone (including non-developers) can create powerful applications with beautiful, consumer-grade user interfaces for any device—all in about 70% less time than it would take by traditional programming.
Twopir Consulting has successfully implemented Skuid on the Salesforce Platform. Skuid provides multiple functionality and best features which can be used by the organizations according to their needs.
Skuid is now part of Nintex. Nintex completed its acquisition of Skuid on January 2, 2024, and the Salesforce product, formerly Skuid SFX, is listed on AppExchange as Nintex Apps for Salesforce. It installs as a managed package, runs in the browser on your org's existing data model, and needs no outside database.
Three parties are involved, and it helps to keep them apart. Nintex licenses the product and owns its roadmap; its behaviour is documented in the Skuid documentation. Salesforce stays the system of record: Skuid pages run as the signed-in user, respect your security model, and every save still runs your validation rules and automation. Twopir Consulting does the work in between: the consultation, implementation and training on this page, as part of our wider Salesforce consulting services.
These are the capabilities organizations use Skuid for on Salesforce. Underneath, they come down to a few building blocks: models that load data from Salesforce and sources such as REST and OData, drag-and-drop components that display it, action flows that run the logic, and design systems that keep every page on brand. Page assignments then decide which profiles, users or record types see which page.
Skuid is not a replacement for Lightning. Salesforce's own point-and-click tools handle standard page layouts, Dynamic Forms and flows well, and custom Lightning Web Components cover what neither tool can. Skuid earns its place in between: screens that span several objects or data sources, or need a branded experience, built without code.
| What you need | Native Lightning tools | Skuid (Nintex Apps for Salesforce) | Custom LWC |
|---|---|---|---|
| Standard record pages and forms | The right tool. Lightning App Builder is point-and-click, and works well for page layouts, Dynamic Forms and flows. | Usually unnecessary. A Skuid page adds a licence and a component to maintain. | Unnecessary. |
| One screen across several objects | Related lists and record pages, one object at a time. | Inline-editable multi-object forms and grids, built with drag-and-drop components. | Possible, with developer time for every change. |
| Data from outside Salesforce on the same page | Needs an integration or a custom component. | Models read Salesforce alongside sources such as REST, OData and SQL, mixed on one page. | Possible through Apex callouts. |
| Branded portals and customer-facing experiences | Experience Cloud builder and its templates. | Skuid pages inside Experience Cloud sites on Aura-based templates (Lightning Web Runtime templates are not supported). | Full control, fully coded. |
| Who builds and maintains it | Salesforce admins. | Admins and builders with the Skuid Page Builder permissions. | Salesforce developers. |
| Licensing | Included with Salesforce. | A Skuid licence for every user who views or builds Skuid pages; other users need none. | No extra licence; developer time instead. |
It is not either-or. The Skuid Page component places a Skuid page on a Lightning App, Record or Home page next to standard components and LWCs, so most orgs mix the two. The Skuid documentation notes that Skuid pages often load one to two seconds after native components on a mixed page, which is one more reason to use Skuid where it adds something. When the answer is code, our Salesforce Lightning app development services and Salesforce developers take it from there.
Skuid supplies the toolkit. Twopir Consulting supplies the Salesforce judgement around it: whether Skuid is the right tool for the job, how it is built inside your org, and whether the people it is built for actually use it.
How to get the Most out of the Skuid for your business use case. We start from the work, not the tool: who uses the screen, what they need from it, and which Salesforce data sits behind it. You leave with a clear answer on where Skuid fits and what to build first.
We build the pages, data models and logic inside your Salesforce org, respect the permissions you already run, and move the work from sandbox to production in a controlled way.
A new screen only pays off when people use it. We train the end users on the workflows built for them, and your admins on maintaining and extending the Skuid pages after we hand over.
A Skuid implementation with Salesforce follows the same discipline as any change to a live org: design before building, build in a sandbox, test with the people who will use it, then deploy and train.
We sit with the people who will use the app, map the records they touch and the clicks they make today, and agree what success looks like before anything is built.
DeliverableUse cases, users and success measures
Which Salesforce objects and other data sources each page reads and writes, and which profiles and permission sets see what. Decided on paper, because it is expensive to change once pages depend on it.
DeliverableSigned-off data and access design
Page layouts drafted in the App Composer and reviewed with users early, so the first version they see is a working prototype rather than a document.
DeliverableClickable prototype, reviewed with users
Pages, models, searching and filtering, and the business logic behind each action, built and demoed in a sandbox, never directly in production.
DeliverableBuilt app, demoed per workflow
Every page tested as each role that will use it, on the devices they use, including the records each role must not see.
DeliverablePassed test plan and user sign-off
A controlled move to production, role-based training for users, and a handover your admins can maintain, with change management for the teams whose screens change.
DeliverableLive app, trained users, admin guide
These are the results Skuid on Salesforce is built to deliver, and the ones our implementations aim at: less time building, fewer clicks for the people entering data, and screens they choose to use.
A Skuid page is only as good as the Salesforce data, permissions and automation underneath it. We build the interface and the org it sits on as one piece of work.
Twopir Consulting has successfully implemented Skuid on the Salesforce Platform, so we know where the toolkit shines and where a native Salesforce feature does the job with less to maintain.
Skuid pages read and write the same objects your flows, Apex, validation rules and sharing model already govern. We design the data model and access first, so the interface does not fight the org behind it.
Fewer clicks, the right fields in the right order, search and filters that match how a team actually looks for records. Adoption is the point of a custom interface, so it is what we design for.
You get pages, models and documentation your admins can maintain, not a black box only we can touch. When you want us to stay, ongoing Salesforce support is a standing offer.
Skuid is a cloud-based, user-experience toolkit for building business applications with drag-and-drop components instead of code. Nintex acquired Skuid in January 2024, and its Salesforce product, formerly Skuid SFX, is now sold on AppExchange as Nintex Apps for Salesforce. It installs as a managed package and works on your org's existing data model, with no outside database.
Yes. It is listed on Salesforce AppExchange as Nintex Apps for Salesforce (formerly Skuid) and is still actively released: Nintex ships a major release each year with updates in between, and supports the current and previous major releases. Twopir Consulting implements and supports it under either name.
No. Skuid pages run as the signed-in user and respect the security model configured in Salesforce, so a Skuid page never shows a user data they could not already see. Saving a record from a Skuid page still runs your validation rules, Apex triggers and other automation, exactly as a save from a standard page would.
Lightning App Builder is Salesforce's point-and-click tool for arranging components on a page, and it handles standard layouts, Dynamic Forms and flows well. Skuid is for screens those tools cannot build without code, such as inline-editable forms and grids across several objects, data from outside Salesforce on the same page, or branded portal experiences. The two work together: a Skuid page can sit on a Lightning page next to standard components.
Every user who views or builds Skuid pages needs a Skuid licence. Viewers are given the Skuid Page Viewer permission set and builders the Skuid Page Builder and Skuid Admin permission sets. Users who never open a Skuid page need no Skuid licence, which is why many orgs use Skuid only for the teams whose screens it improves.
Yes. Skuid pages are metadata, so they can be stored in GitHub or Bitbucket, and the skuid-sfdx plugin is the main way to move them between orgs. Some related metadata still has to be moved separately, so we plan deployments from sandbox to production as part of every implementation.
Three things: consultation on how to get the most out of Skuid for your business use case, Skuid implementation with Salesforce, and training of users. In practice that means use-case discovery, data model and access design, a prototype reviewed with users, a sandbox build, testing by role and device, and a controlled deployment with training and handover.
In a fast-evolving business world, the ability to customize and adapt technology to specific needs is crucial. Skuid integration with Salesforce provides the flexibility to create tailor-made solutions without relying heavily on code.
With its powerful no-code/low-code platform, Skuid enhances user experiences, productivity, and business efficiency.
A first conversation covers who uses the screen, the Salesforce data behind it and where clicks and time get lost: enough to say whether Skuid is the right tool, what a first build would cover, and how we would train your users. No obligation to proceed.
Talk to a Salesforce architect who implements Skuid
