Hub sites for news, documents, and day-to-day collaboration, designed around how your teams work and built inside the Microsoft 365 tenant you already have.
Start with the intranet, or pair it with a migration, a workflow, or an app. Same team either way.
A branded home for news, policies, documents, and people, laid out so someone new can find the front door.
Move from file servers, Google Drive, Dropbox, or an older intranet, cleaned up on the way.
Libraries, metadata, and search designed so files are found, and the right people can open them.
Replace email chains and manual handoffs with Power Automate flows that run on a schedule, a form, or a file.
When a spreadsheet is doing the job of an app, we replace it with a Power App on SharePoint or Dataverse.
Chronodat publishes SharePoint Framework apps for the jobs that show up in almost every tenant, and builds a custom web part when yours is specific.
Tell us which one sounds like you. A short call is enough to pick the path.
Files elsewhere
Move what is still used into a structure people understand, then give it a front door.
Plan the moveExisting tenant
Untangle sites, permissions, and libraries so search and access both make sense.
Low traffic
Rebuild it around the news, people, and documents that give someone a reason to come back.
Manual work
Turn the processes that eat the week into flows and apps.
See automationWe map the teams, the content, and the pain, and agree what “done” looks like.
Scope, sequence, and price before build starts, so the work is clear on both sides.
Pages and libraries take shape in your tenant, with check-ins so you can steer.
Owner training, a short handover, and a way to reach Chronodat after the first week.
The same engineers who publish Chronodat apps for Microsoft 365 design the intranet around them.
The intranet, the libraries, and the lists stay in Microsoft 365. Nothing is copied to an outside database to “run the site.”
You talk with the Chronodat team that will design and build it, not a rotating cast of hand-offs.
Most of the build uses SharePoint you already pay for. Anything that needs an extra licence is named in the proposal.
Notes from people who use Chronodat products and support, not a script written for this page.
Easy to install, nice user interface and great set of features. I really like the quick support from the product team.
Tom Hamson · Admin IT Support
We implemented the Chronodat Help Desk application. It works well, and it integrates easily with SharePoint. Staff can check the status of their requests.
Lisa Massengill · IT Specialist
Great app and support. The support team were able to make changes to the app for us for a reasonable cost. They have been helpful and responsive.
D Dornan · UX Designer
A focused hub with news, navigation, and the main libraries is often ready in a few weeks. A tenant with many departments, a migration, or a lot of cleanup takes longer. You get a timeline in the proposal before work starts.
SharePoint Online is included with Microsoft 365 business and enterprise plans. We build on that tenant. If a workflow or app needs a premium Power Platform licence, that is written into the proposal before you commit.
Yes. Plenty of projects start from a tenant that already exists: tidying sites and permissions, repairing navigation, or replacing an intranet nobody visits.
Yes. That work is the migration service. We audit first, then move what should live in SharePoint into libraries and metadata instead of copying the old folder tree as-is.
Yes. Modern pages take your colours, logo, and imagery. If the stock web parts cannot do something you need, we can build a SharePoint Framework part for that page.
Site owners get a walkthrough and short notes: how to post news, where libraries live, and who to ask. Later changes can stay with your team or come back to Chronodat.
A short call is enough to see whether you need a new hub, a cleanup, or a migration first.
Request a proposalWhen the page needs a directory, search, or a permissions review, these already exist.
