Content held in your records
The text, pages and sections of the website are kept in your own records. Changing them does not mean editing code.
Websites and Portals
Pages and portals built on your own records. Your team can edit them directly or by asking an assistant, so small changes do not wait for a developer.
The problem
Changing the website needs a developer, and what it says drifts away from what your records say.
What you get
The words on the site come from records your team already keeps.
The text, pages and sections of the website are kept in your own records. Changing them does not mean editing code.
Your team can ask an assistant to prepare a change in plain language, such as a new section or a corrected line. You decide who is allowed to make changes.
News, events, services and prices can be changed quickly and appear on the site without a new release.
A client can have a page or portal that shows their own information, and only theirs.
Who does what
An example
A site your team edits from the records it already keeps.
The text, images and lists on the site are kept as records your team already knows how to edit.
Sample: Services table: name, summary, price
A change is made directly in the record, or by asking an assistant to make it, and then saved.
Sample: Price updated, saved
The change is copied to the database the site reads from, within a minute or so.
Sample: Sync completed in 12 seconds
The live page shows the new text. Nothing was rebuilt, and nobody had to wait for a developer.
Sample: New price live on the page
A page where each client sees only their own information.
A client is given access A private link for each client. Each client receives their own link or sign-in to a page built for them. Sample: Link sent to the client
They see only their own work Status, files and next step. The page shows that client's quote, files and progress, and nothing that belongs to anyone else. Sample: Quote, photos, next step
They can book or reply Book a time or send a message. A client can book a time or send a message from the same page, and it lands on their record. Sample: Booked Thursday 10:00
Your team sees it at once One record, two views. What the client does appears on the same record your team works from, so there is nothing to copy across. Sample: Booking appears on the client record
Connects to
Common examples of what it can be connected to. If a tool has an inbox or an API, we can usually connect it.
What changes
Small changes no longer wait for a developer.
A corrected line or a new section does not have to wait for a developer.
The website draws on the same records your team already keeps, so it does not drift out of date.
How it works
One session on what changes often, then a site built on your records.
We start with one working session on which parts of the site change most often, who changes them, and which records they come from.
We build the website so that its content comes from those records, in your own account.
We show your team how to make changes. If you want it maintained, we review once a week what changed and what needs a decision from you.
The people you choose. You decide who can change what.
Yes. An assistant can be connected to your records to prepare changes in plain language. We agree with you which changes it may make.
No. We build the structure and connect it to your records. If you already have a brand and a design, we work to it.
In many cases we can connect the existing site to your records instead of starting again. We look at it in the first session.
Yes. The content stays in your account, and you can export it.
Pairs well with
Each service works alone. These are the ones that make it work better.
Book a call or send us a message, and we will come back to you.