Lukco
Book a call

Websites and Portals

Websites your team can update.

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

Every change waits for a developer.

Changing the website needs a developer, and what it says drifts away from what your records say.

What you get

A site that follows your records.

The words on the site come from records your team already keeps.

  • 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.

  • Update by asking

    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.

  • Built for content that changes often

    News, events, services and prices can be changed quickly and appear on the site without a new release.

  • Pages for your clients

    A client can have a page or portal that shows their own information, and only theirs.

Who does what

We handle the routine.You decide.

We handle

  • Builds the site so its content comes from your records
  • Syncs changes from your records to the live site
  • Builds client pages that show only a client's own information
  • Shows your team how to make changes

You decide

  • What changes often and who changes it
  • What each client can see
  • Who may change which pages
  • Whether your team edits directly or asks an assistant

An example

A new service is added

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

Connects to

The tools you already use.

Common examples of what it can be connected to. If a tool has an inbox or an API, we can usually connect it.

  • Airtable
  • Google Calendar
  • Cal.com
  • Resend
  • Vercel
  • Your CRM

What changes

Change it yourself.

Small changes no longer wait for a developer.

  • No developer for small changes

    A corrected line or a new section does not have to wait for a developer.

  • The site and the records agree

    The website draws on the same records your team already keeps, so it does not drift out of date.

How it works

Agree, build, hand over.

One session on what changes often, then a site built on your records.

  1. 01

    Agree what changes often

    We start with one working session on which parts of the site change most often, who changes them, and which records they come from.

  2. 02

    Build the site on your records

    We build the website so that its content comes from those records, in your own account.

  3. 03

    Hand over and review

    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.

Common questions

Who can change the site?

The people you choose. You decide who can change what.

Can the site be changed by asking an assistant?

Yes. An assistant can be connected to your records to prepare changes in plain language. We agree with you which changes it may make.

Is this a design service?

No. We build the structure and connect it to your records. If you already have a brand and a design, we work to it.

What if we already have a website?

In many cases we can connect the existing site to your records instead of starting again. We look at it in the first session.

Can we take the content with us?

Yes. The content stays in your account, and you can export it.

Tell us what isgetting in the way.

Book a call or send us a message, and we will come back to you.

Get in touch