Forge builds real applications on SmartLinks: customer and business experiences with identity, data, permissions, execution and AI already in the same platform. Connected products are where it shines.
Forge builds public sites as well as customer, team and product experiences. They can share the same foundation for people, products, data and permissions. A scan is one way in, not the whole story.
Built in Forge
Business websites
Public pages · product content · enquiries
Customer engagement
Campaigns · games · competitions · fan experiences
Business workspaces
Product content · operations · partners
Digital product passports
Materials · provenance · repair guidance
Workforce & field apps
QR/NFC scans · RFID on supported devices · jobs
AI experiences
Assistants · recommendations · content
And the bespoke applications your business needs.
Shared foundation · products & people · custom records · access · server functions · integrations
What people build on it
Five ways in. One platform underneath.
Start with a product, its content, a campaign, a public website or an integration. Forge builds each on the same SmartLinks foundation, so the work can connect as your business grows.
01
Marketing & engagement
Campaigns with a real platform behind them.
Competitions, quizzes, votes, spin-to-win, fan engagement — entered from a social post, an email link, a TikTok, or a scan. Every entry lands in your own CRM, ready to segment, journey and message across email, SMS and WhatsApp. No bolt-on contest tool, no exported spreadsheet.
Scan a QR code, tap an NFC tag, read an RFID label — the physical thing opens a digital experience tied to that exact item. Registration, warranty, service history, authenticity, manuals, loyalty: the product itself becomes the channel.
Studio manages the details, content and media around your products. Forge can turn them into a public product website, a support experience or a tool for your team — without duplicating the product editor.
Build public pages that tell your story and connect to the products, content and enquiries behind it. The site can be tailored to your business while Studio remains the place to manage platform data.
Describe the flow in plain words — when a product changes, send it here, shaped like this. Forge builds it on the platform's integration layer: server functions, event triggers, field mappings and sealed credentials.
The scan opens an experience connected to that individual item.
02
A technician services
The work and its history stay with the item, not a disconnected form.
03
The business follows through
The right people can see the relevant record and take the next action.
Workforce & field operations
Turn a scan into a completed job.
Build mobile workflows for inspections, stock checks, servicing and handovers. A scan can identify the exact item; forms, records and cases carry the work forward for the team.
01
Identify
Scan a QR code or tap NFC; supported specialist devices can also read RFID.
02
Do the work
Follow a tailored checklist, capture a reading or report a fault.
03
Keep the record
Save the result against the item or an app-specific case.
04
Move it on
Give the next person a status, history and clear next action.
RFID reading requires compatible hardware and the supported operator app; it is not available in every phone or browser.
Marketing, CRM & communications
A full engagement engine, already built in.
Competitions, quizzes, votes, spin-to-win, fan engagement — the campaigns brands usually bolt on as a separate tool. Here they're part of the platform: every entry lands in your own CRM, ready to segment, journey and message. And entry can start anywhere — a social post, an email link, a TikTok, a QR code on pack. The scan is one door, not the whole house.
Most app builders stop at the screen. SmartLinks includes the whole marketing loop behind it: tracking what people do, running journeys, building audiences and messaging them across every channel.
EmailSMSWhatsAppPushWallet passes
01
Track
Every scan, registration, entry, vote and page view is recorded as an interaction against the person and the item.
02
Journey
Journeys react to what people do: welcome a new owner, nudge an unfinished registration, follow up after a service.
03
Segment
Build audiences from real behaviour and product ownership, not just a mailing list.
04
Communicate
Reach each segment on the right channel, with consent and topic preferences respected at send time.
The toolsets behind it
Multi-channel template studio
Design, configure and edit email, SMS, WhatsApp, push and wallet messages in one place. Preview and send a test before anything goes out.
Liquid template library
Personalise with live product, item, owner and contact data. The same template language works across messages, pages and documents.
PDF & document tools
Read PDFs, decks and documents into usable data with AI, then generate, fill and merge PDFs of your own: certificates, warranty cards, reports and forms.
Print Studio
Design and generate print-ready labels, QR codes, tags and packaging artwork straight from live product data — no separate design handoff.
Broadcasts & transactional sends
Run campaigns to whole audiences, or send one message automatically when something happens, such as a claim or an ownership transfer.
Loyalty
Reward repeat engagement and keep customers coming back to the products they own.
Analytics
See scans, clicks and outcomes, and understand which experiences and messages actually work.
Channels like SMS and WhatsApp need to be set up for your brand. Consent rules and suppression lists apply to every send.
AI & integrations, already there
AI tooling, built in
Web search and page reading, document and PDF parsing, image understanding and generation, brand research and voice — available to every app and every workflow without wiring up your own AI accounts.
Integrations without the plumbing
Send transactional email, scrape and read websites, call webhooks and connect external systems through managed integration flows. Credentials stay sealed server-side; your app just uses the capability.
The things other builders bolt on
Where general app builders ask you to connect an email service, a scraping service and an AI provider yourself, SmartLinks ships equivalents as platform features — already secured, already billed, already working.
Not a contest widget
Giveaway tools lock you into templates, cap your participants and hand you a spreadsheet to export. Here every entry is already in your CRM, with the audience and the follow-up built in.
Not an enterprise cloud
The big engagement platforms have the CRM and the journeys — but no competition, quiz or vote mechanics at all. You'd be buying a second tool and stitching it back in. Here it's one system.
Not a template library
Gamification platforms sell you fixed game formats billed per player. Forge builds the exact experience you describe — on-brand, on your data, with no per-participation meter running.
What sits behind every app
A platform, not a pile of screens.
A beautiful interface is only the visible layer. The context, objects and services beneath it are why the experience can work in the real world.
01
Experiences
Portal · Hub · websites · mobile teams
02
Connected context
Products · individual items · people · ownership
03
Data & intelligence
Records · cases · conversations · journeys · AI
04
Execution & exchange
Server functions · events · integrations
01 / 06
The experience layer
One physical thing. Many ways in.
A scan opens the mobile Portal. Teams work in Hub. The same connected product context can power a public page, a compact widget or a focused app.
Portal
The mobile experience a customer opens by scanning or tapping a physical item, with navigation and sign-in when needed.
Hub
The desktop home for product content, item history and ongoing business administration.
Beyond the shell
Public web pages, customer and partner portals, small embedded views and Sidekick screens for staff on the move.
02 / 06
The context layer
The item is the starting point.
Not another generic form detached from reality. SmartLinks knows which collection, product, individual item and person the experience is about.
Product to individual unit
Collections, products, variants, batches and proofs give every physical unit a place in the model — a foundation for your own digital product passport.
People & ownership
Contacts, sign-in, claims and ownership connect the right people to the right things.
Scoped access
Public, owner and admin views can expose different information; personal fields have their own boundary.
03 / 06
The data layer
Useful objects, not an empty database.
Start with the platform’s product and customer model, then add app-specific data that follows the work your team actually does.
Records
Custom structured objects for registrations, inspections, content or any other app-specific data, scoped to a product or item.
Cases
Track requests and work through statuses and history, from a warranty claim to a service issue.
Threads
Conversations and replies tied to a person, product or item.
04 / 06
The engagement layer
Build the relationship after the scan.
From playful marketing to lasting loyalty: track interactions, run journeys, segment audiences and message them by email, SMS, WhatsApp, push or wallet.
Interactions, journeys & segments
Record entries, votes, scans and registrations, trigger journeys from what people do, and build audiences from real behaviour.
Multi-channel comms & templates
A template studio with a Liquid library for personalised email, SMS, WhatsApp, push and wallet messages, as campaigns or automatic one-to-one sends, with consent built in.
Documents, print & loyalty
Parse and generate PDFs with AI assistance, design labels and QR codes in Print Studio, reward repeat engagement, and see what works.
05 / 06
The execution layer
Real logic, without a server to run.
When an app needs more than a screen, server-side functions can respond to requests, events or schedules. Credentials stay on the server side.
Server functions
Run app logic behind controlled public or admin access, or in response to platform events and schedules.
Sealed secrets
Keep external credentials out of customer-facing app code and resolve them only for server-side work.
Privacy by design
Use scoped visibility and consent tools as building blocks. Your own data handling and legal obligations still need review.
06 / 06
The extension layer
Connect intelligence and existing systems.
SmartLinks is the connected product layer alongside your existing systems, not a replacement for the CRM, PIM, ERP or finance tools that already do their jobs.
AI & integrations, built in
Platform AI chat and assistants, web search and page reading, document parsing, image and voice — plus managed integrations for transactional email, web scraping and webhooks, with credentials sealed server-side.
Inbound calls & webhooks
Expose controlled HTTP functions to receive external requests and webhook events; verify callers in your function.
Outbound integrations
Send mapped SmartLinks data to other systems on demand or from events. Scheduled flows are documented as an upcoming increment.