Marketing: Your whole content plan on one screen.
And nothing unapproved goes out.
A social-media publishing calendar, content approval and campaigns in one app. No more plan in Excel and comments scattered across email and chat.
Runs in your Microsoft 365 — no third-party scheduler, no keys to your networks.
Three steps anyone can manage.
The whole process fits in one paragraph — and your people will find it just as easy.
-
You plan the content
Posts, activities and events from the CRM in one calendar — month, week or agenda. A click on a day creates a post with the date filled in.
One text, variants for each network -
Content goes through approval
0–3 steps you define, with a decision history and send-back with a comment. Approved text locks.
Nothing unapproved goes out -
You publish by hand, no keys
For each network you copy the finished text with hashtags and open its editor. Then you mark the post as published.
Your accounts and content stay under your control
What it looks like in practice
A post calendar for the whole month, a kanban from idea to publication, and a two-step approval of a post right in its detail, including texts for each network.
Today vs. with EP365 Marketing
This is what marketing teams tell us before they deploy EP365 Marketing.
For the first time we see our whole content plan on one screen, and nothing unapproved goes out any more.
Deployment was done in half a day, with no IT involvement. The team set up the networks, topics and approval steps themselves in a short workshop.
30 minutes on screen, no company presentation
- 5 minYour marketing today — what frustrates you most about planning and approvals
- 10 minThe publishing calendar, a post and approval through the content team's eyes
- 10 minCampaigns, activities, tasks and event prep through the marketing lead's eyes
- 5 minWhat a rollout would look like for you + an indicative price
Publishing calendar
Posts with an editorial workflow
Text versions of a post
Configurable approval
Campaigns, activities and tasks
Collaboration and conversations
Manual publishing with no API keys
Publishing plan and Overview
Tasks and the Outlook calendar
Event support from the CRM
Writing with AI over company knowledge
Code lists and branding under control
Roles protected by SharePoint permissions
Marketing on a phone
Everything clearly in one window
Content stays with you
Posts, campaigns, visuals and the whole plan are stored exclusively in your Microsoft 365 environment, under your company identity and permissions. No export to a third-party cloud, no content migrated out.
No keys to your networks
The app doesn't publish through social media APIs — it needs no access to your accounts and no tokens. Publishing stays in your team's hands and the content under your control.
No new passwords
People sign in with their company Microsoft account. When a team member leaves, IT handles it in one step — blocking the account also removes access to the marketing content.
Only roles write, SharePoint holds the line
Administrator, approver, team member and read-only guest — access is governed by your company identity, and an Entra ID group can be placed in a role too. Posts, campaigns, activities, tasks and comments are written to only by the Administrator, Approver and Team member roles and the site owners, enforced by SharePoint permissions rather than just the app's interface; everyone else on the site keeps read access. The Data lists card in Settings measures the permissions of every list and shows who has extra access.
Only the licence request reaches us
From us the app downloads only its code, fonts, the what's-new and version overviews and your licence file (company identifier and expiry date) — and checks the licence in your browser. No marketing content is sent to us, and while you work with the app no connection goes anywhere outside Microsoft and EasyPortal 365. The optional AI writing assistant uses your own AI service in Azure (EP365 AI Assistant).
Verified app code
The app's code is digitally signed. Before it starts, the app verifies the signature — including the parts it loads later on demand — and code that fails the check does not run. Instead, a plain message says the version could not be verified, and the help explains what to do.
Verifiable history and IT-free deployment
Who approved or changed what and when is traceable in the record history and in the Microsoft 365 audit; versions of a post's text are stored in the SharePoint version history. You deploy the app as a single package — the required lists and groups are created automatically, with no manual scripts.
Price by company size
You pay per company, not per team member. The price is based on the total number of internal users in your Microsoft 365 — the full scope of the app within that size band.
On-site implementation
Installation, environment preparation, a workshop for the marketing team, theming to match your brand, configuration of networks, topics, hashtags and approval steps, and optionally preparation of a publishing plan and event-prep templates.
The fixed price covers a standard rollout. A more extensive initial setup beyond a standard rollout. We will send a precise quote after a short call.
Support pricing
Consultations, environment adjustments, custom code lists or onboarding new team members.
Support is billed per started 15 minutes of work. We always tell you the expected scope in advance.
Where is our marketing content stored?
Does the app publish to networks automatically?
Do we need Power Automate or Azure?
How does content approval work?
What if we schedule a post directly in the network?
Can an older wording of the text be restored?
Does EP365 CRM have to be connected?
How quickly can we deploy it?
Does it work on mobile?
How do app updates work?
Often paired with EP365 Marketing
Further reading on the blog
Need help putting your SharePoint in order first? Explore our audit, governance and care services
What exactly do you want to discuss?
Pick what's burning most right now. We'll get back to you, walk through your situation and propose next steps, including an indicative price.