CITADEL//MATRIX

Web application development · Michigan Custom web apps,
built around people.

Customer portals, internal tools, dashboards, and full custom web applications — built to order for Michigan organizations around the people who use them, the work they do, and the decisions they make.

Request a web app How a project works
Module specMOD_02
  • FORStaff · customers · partnersby role
  • RUNSIn the browserany device
  • BUILTFrom your requirementsto order
  • PROCESSRequest → delivery5 steps

01 What we build

Applications
with a job to do.

A web app is software people use to get work done in the browser. It starts with the job, the people doing it, and what gets in their way today.

  • app.portal

    Customer and partner portals

    A secure place for customers or partners to sign in, see their information, submit requests, and follow progress.

  • app.internal

    Internal tools

    Purpose-built tools for the jobs your team does every day, replacing workarounds and shared spreadsheets.

  • app.dashboard

    Dashboards and reporting

    The numbers and statuses people need, in one place, drawn from the data you already have.

  • app.roles

    Role-based workspaces

    Different views and permissions for different roles, so each person sees what their work requires.

  • app.records

    Data entry and approvals

    Structured forms, validation, and approval steps that keep records complete and decisions traceable.

  • app.devices

    Works on any device

    Interfaces that adapt to desktops, tablets, and phones, with nothing to install.

02 Signs it’s time

When the workaround
becomes the work.

Custom web apps earn their place when a process matters, repeats, and doesn’t fit the tools you have.

  • A spreadsheet runs a process. It has grown tabs, colors, and rules that only one or two people fully understand.

  • The same information is entered twice. People copy data between email, documents, and systems by hand.

  • Customers ask for updates you have to look up. Status questions take time a portal could answer.

  • Off-the-shelf tools almost fit. The last part of your process lives in workarounds.

  • Access is all or nothing. Everyone sees everything, or the right people can’t see what they need.

  • Nobody sees the whole picture. Information is scattered, so reporting means assembling it by hand.

03 Planned and built

Shaped by your process.
Engineered underneath.

The requirements meeting maps the work. The build turns it into software that holds up in daily use.

Requirements Planned together

  • Who will use it, and in which roles
  • What each role needs to see and do
  • The process it supports, step by step
  • The data it stores and where it comes from
  • What it connects to

Engineering Built in

  • Sign-in and role-based access
  • Validation that keeps records clean
  • A history of changes where decisions matter
  • Responsive interface for every screen
  • Testing before delivery

04 How it works

From request
to working software.

Every web app project follows the same five steps. Nothing is built until you’ve approved a quote.
The full process

  1. 01 / Request

    You send a request.

    Describe the process, the people involved, and what isn’t working.

  2. 02 / Meet

    We gather requirements.

    Roles, steps, data, and connections, agreed together.

  3. 03 / Quote

    You receive a quote.

    A quote for the app, based on the agreed requirements.

  4. 04 / Payment

    Payment is collected.

    When you accept the quote, payment is collected and work begins.

  5. 05 / Deliver

    We build and deliver.

    Your app is built, tested, and delivered to you.

05 Queries

Web app
questions.

app.01What is the difference between a website and a web app?

A website mainly presents information. A web app lets people do work: sign in, enter and update data, follow a process, and see results that change with what they do. Many projects mix both.

app.02Who can use a custom web app?

Whoever you decide: your staff, your customers, partners, or a mix. Access is planned around roles, so each person sees and can do what their role requires.

app.03Can a web app replace our spreadsheets?

Often, yes. Spreadsheets that hold shared processes, approvals, or records are a common starting point. We look at how the spreadsheet is really used before deciding what the app should do.

app.04Does a web app work on phones?

Yes. Interfaces are built to adapt to screen size, so people can use the app on desktops, tablets, and phones.

06 Keep exploring

Related
modules and guides.

07 Start with a request

Have a process
that deserves an app?

Tell us how the work happens today. A rough description is enough to begin.