On Data Visions, the people who know the work build the tools for it. You describe what your company needs, and the platform takes care of the hard parts: security, sign-in, data, backups, and keeping your workspace's records away from everyone else's. You don't need to be a developer.
This page covers what you can build, how modules and websites differ, the ways to build them, and where to start.
What you can build
There are two kinds of things you can build:
- Modules are tools your own people use inside your workspace, such as a job tracker, an inspection checklist, a bid log or a tool crib. They're for the work your company does every day.
- Websites are what the public sees: your company site, a careers page, a page that takes contact requests. They're for customers, visitors and people applying for jobs.
Many companies build both and connect them, for example a website contact form that creates a lead in your CRM module.
Modules vs websites
| Module | Website | |
|---|---|---|
| Who uses it | Your people, signed in to your workspace | Anyone on the internet |
| Where it lives | In the sidebar of your workspace | At its own address, such as yourcompany.com |
| What it holds | Your records: jobs, people, equipment, time, files | Pages and pictures. It shows only what a module offers it |
| Who sees what | Set by roles and permissions | Everyone sees the same pages |
| AI | Comes with its own AI agent | No agent. It can send what visitors type into a module |
| Goes live when | A Workspace Admin publishes it after the module check | Someone with Publish websites publishes a version |
| Where to read more | Build a module with the Module Builder | Websites: how they work |
Rule of thumb: if your own people sign in to use it, build a module. If the public will look at it, build a website. If the public needs to send you something, such as a request or a job application, build both: a website for the form, and a module where the requests land.
Three ways to build
| Best for | |
|---|---|
| The Module Builder | Describing what you need in plain words and watching it get built. Builds modules and changes websites. Start here. |
| Claude and the connector | People who already work with an AI assistant. See Build modules with Claude and Websites with Claude and the command line. |
| The command line | Developers, web designers and very large modules. See The command line (CLI). |
All three work on the same versions, so you can mix them. A web designer can make the first version of your website, and you can change it later in the Module Builder. Nothing goes live until someone with permission publishes it.
What a module can do
A module isn't only screens and records. It can use what the platform already provides:
- Files, email and notifications. Keep files and photos, send email, and alert people when something needs them. See Platform services for modules.
- Your other modules. Share records with them, so a job knows its customer, crew and costs. See Connect modules to each other.
- Its own AI agent and automations. Run work on a schedule or the moment something happens. See Automations: agents, triggers and schedules and Agent tools, skills and scripts.
- Outside systems. Microsoft 365, computers in your own building, and the websites your people already use. See Connect to outside systems: Microsoft 365, the Bridge and APIs and Agents in the browser: the browser extension.
- Reports and dashboards. See Datasets.
What a website can do
- Live information from your workspace, such as open jobs, through feeds that a module offers.
- Forms that send to a module, such as contact requests that become CRM leads.
- Your own domain, such as yourcompany.com. See Use your own domain.
- Versions you can preview and roll back. See Versions, preview, publish and roll back.
Customer sign-in on a website, where customers see their own records, isn't available yet.
Getting started
- Pick one small job. Choose something your team does every week, such as a visitor log, a tool sign-out sheet or a vehicle inspection. A small first module teaches you how it all works.
- Open the Module Builder. Click Module Builder in the sidebar (Workspace Admins only). Describe what you need in a couple of sentences and click Start.
- Plan it with the builder. It asks who will use the module and what they need to do, and agrees a plan with you before building anything.
- Try it in your development copy. Everything is built in a copy of your workspace, so you can't break anything that's live. Click through it the way your people would, and ask for changes until it's right.
- Publish it. Click Publish. The module goes through the module check, then appears for everyone whose role allows it. See Publish a module: the module check.
- Then add a website if you need one. Create it under System settings → Websites. See Websites: how they work.
Then share it
If you build something other companies could use, list it on the Marketplace and earn a share of what they pay. See List a module on the Marketplace.