Skip to content
Coditu

SharePoint · Internal apps

You pick the building blocks. We build your app.

We build internal software for small and mid-size companies: ready-made building blocks for your Microsoft 365, in your design, with your login. You see every step on a shared board.

Send us a small request, we'll build it for free.

1 task per client · one screen or one feature · in up to 3 days

  • First app in 1–3 days
  • You see every step on the board
  • Runs in your Microsoft 365
  • Mohamed Tamer
  • Abdelrahman Elkhateeb
  • Ahmed Yehia
  • Adam Nafie

Your team · Berlin · Cairo

Example: building blocks become a booking app – with a dashboard, bookings, a calendar and a login.

Your intranet, modernised

Many SharePoint intranets look dated and are hard to use day to day.

Drag to compareExample: the same news page twice. Before, a classic SharePoint intranet with a grey bar, a list of links and a small table; after, our design with an area filter and large cards. Example · sample data
Example: a member of staff edits a news post in our news desk app and publishes it. Next to it, the post appears at the top of the intranet home page. Example · sample data
  • Stays in your Microsoft 365

    Posts, events and pages stay in your SharePoint lists.

  • Same login & permissions

    Your team signs in with their Microsoft account. Your groups decide who may edit what.

  • Nothing to migrate

    Your content stays where it is. We renew the interface.

How it works

  1. 01

    Send a screenshot

    A picture of one old web part is enough to start.

  2. 02

    We redesign it for free

    We redesign it and show you the result, in up to 3 days.

  3. 03

    We modernise the rest

    If you like it, we renew the rest of your intranet step by step.

Get one web part redesigned free

Your free small task · 1 per client · in up to 3 days

The Baukasten

Our flagship — we call it the Baukasten: a library of building blocks for your Microsoft 365, in your design, with your login, on your own server.

  • Blocks that fit together

    React components in your design that snap together like building blocks — a form, an approval, a dashboard.

  • Sign-in with Microsoft Entra

    Everyone signs in with their Microsoft account and sees only what their permissions allow.

  • On your own server

    Runs on your intranet domain. Your data never leaves your system.

  • For requests, approvals and more

    Forms, approvals, dashboards and directories — built from the same blocks.

In production
6+ appsat one organisation in Germany
  • Requests
  • Onboarding
  • News editing
  • Editorial calendar
Illustrative only, no real client data.

What we build — and the problem it solves

Three examples from real projects, rebuilt with example data.

Area: All areas

Rebuild of a calendar web part on an intranet: a filter by area, four weeks with marked events and, beside them, the next events from a SharePoint list. Rebuild · example data

SharePoint web parts

“Our intranet is cluttered and out of date.”

Web parts that slot into your existing SharePoint pages and show your lists live.

Result

More than 40 web parts for one organisation, mostly 1–2 days per web part.

Status at a glance: Planned / Draft / Published

Rebuild of an editorial planner: signed in with Microsoft, one week with a row per channel, each post with its area, status and editor. Rebuild · example data

Internal apps

“We still do this on paper, in Excel and by e-mail.”

Small, focused apps built from your sketch — for requests, onboarding or the editorial plan.

Result

A first version in 1–2 days, with Microsoft sign-in and rights by group.

Rebuild of the NVRMiss home page: one headline, one button for beta access and small glimpses of the product — calls, reminders, calendar. Rebuild · example data

Websites & web apps

“Our website is slow or looks dated.”

Fast websites and product pages, built to be found on Google.

Result

A page that says straight away what you offer — on a phone as on a desk.

Not sure what fits? Send us your sketch.

How we work — and you see every step

Every task sits on a shared board. You see what is being built, what is waiting for your feedback and what is live.

Project board

Example

Sketch

02
  • Editorial calendar
    AppAN
  • “Cost centre” field in the request
    ChangeAY

In progress

01
  • Onboarding checklist
    AppAE

Review

02
  • New link in the main navigation
    Web partMT
  • Banner on the home page
    Web partMT

Live

01
  • Intranet news with approval
    Web partAE
All data is illustrativeClient view · read-only
  1. 01

    Sketch & call

    You send us a sketch, a photo or a few sentences. On a call we work out what the app has to do.

  2. 02

    First version in 1–2 days

    First you get something to click through. A first app version takes us about 10 to 14 hours of work.

  3. 03

    Weekly sprint & feedback

    Every week we show what is done and you tell us what should change. The board shows what we are working on.

    From practice

    Weekly sprints with the same client for almost a year

  4. 04

    Go live & maintenance

    When everything fits, the app goes live. After that we stay on hand for changes and maintenance when you need them.

One intranet, built week by week

For an organisation in Germany we build and maintain its SharePoint intranet. For almost a year, in weekly sprints.

Client
An organisation in Germany
Project
SharePoint intranet
Period
Almost a year · weekly sprints

From the project

  • 40+web parts for one organisation
  • 5–10 hfor a new web part, mostly 1–2 days
  • 10–14 hfor the first version of an internal app
  • ≤ 2 hfor most change requests

Web parts

The building blocks the intranet's pages are made of.

  • News & communication
  • Navigation & search
  • People & org chart
  • Page layout
  • Media & polls

Internal apps

Standalone apps inside the intranet — for the editorial team and for new colleagues.

  • News editor
  • Editorial calendar
  • Onboarding
Example
Example: an intranet home page made of web parts. Our own drawing, no client data.
Client anonymousIllustration only

More projects

  • NVRMiss home page
    Product site

    NVRMiss

    Product site for B2B software for service businesses: features, how it works, pricing, FAQ.

  • Nile Atelier home page
    Website

    Nile Atelier

    Website for an Egyptian fashion label, with collection and journal.

What happens to your data

How we handle your data, your access and your code.

  • Your data stays in your system

    We build directly inside your Microsoft 365 and SharePoint. Your data lives with Microsoft, not with us — we have no servers of our own for it.

  • Permissions stay in your hands

    You grant us access to your Microsoft 365. Your own permission groups control who can see and edit what.

  • A clean handover

    You get the code, the documentation and full control. There is no lock-in.

  • No passwords in code

    Keys and passwords live in their own protected store — never in code and never in chat.

Example
Example: web parts and apps run in your SharePoint. Our own drawing.

What it costs

The price depends on the amount of work. These are the figures we start from.

  • Per web partfrom €600Depends on scope, usually 5–10 hours of work.
  • Per hour€70 per hourFor ongoing changes and smaller tasks.

Larger projects get a discount — and a little extra on top. Before we start, you get an estimate from us. All prices net.

See all prices and billing models

Common questions

Short answers on cost, speed, working together and your code.

  • What does a project cost?

    The price depends on the amount of work – from €600, €70 per hour for ongoing changes. Larger projects get a discount, plus a little extra on top. Before we start, you get an estimate from us. All prices net.

  • How soon is there a first version?

    A new web part usually takes 1–2 days. The first version of an internal app is ready in a few days.

  • Do you only work with SharePoint and Microsoft 365?

    No. We build SharePoint web parts, internal apps, websites and frontends — and look after them after launch.

  • What does working together look like?

    We work in weekly sprints. Every week we show what is done and you tell us what should change. You have one fixed contact.

    How we work
  • You are in Berlin and Cairo. How does that work?

    Your fixed contact is Adam Nafie in Berlin. Berlin and Cairo are at most one hour apart. We talk with you in German or English.

  • Who owns the code?

    You do. You get the code, the documentation and full control. There is no lock-in.

  • What happens after go-live?

    We stay on hand for changes and maintenance when you need them. Billed per request.

Send us your request

A few sentences are enough. If you have a sketch or files, attach them.

Or straight to contact@coditu.com

You get a personal reply from Adam in Berlin.

Your contact in Berlin

  • Adam Nafie

    Client partnerships

From the first call to go-live, you talk to the same person.

Your team in Cairo

  • Mohamed Tamer

    Frontend Lead

  • Abdelrahman Elkhateeb

    Frontend Engineer

  • Ahmed Yehia

    Backend & DevOps