Skip to content
Let’s talk ↗
Services

Six practices

The six practices behind one delivery process.

Talk to us →
Services

Software & web

Websites, applications, APIs, mobile and database work.

Talk to us →
Services

Cloud, data & AI

Azure, data engineering, analytics and applied AI.

Talk to us →
Services

Marketing & growth

Search, content, conversion and measurement.

Talk to us →
Services

Recruitment

Hiring through Incipit and working at Incipit.

Talk to us →
Services

Travel & experiences

Itineraries and journeys planned around the traveller.

Talk to us →
Industries

By industry

Sector context for the work.

Talk to us →
Industries

Business solutions

Solution patterns we build repeatedly.

Talk to us →
Products

Products & platforms

Each product at its real stage.

Talk to us →
Products

Support & releases

Each product at its real stage.

Talk to us →
Work

Portfolio & proof

What can be evidenced, labelled honestly.

Talk to us →
Resources

Articles & insights

Articles, guides and self-service help.

Talk to us →
Resources

Help & knowledge

Articles, guides and self-service help.

Talk to us →
Resources

Start a project

Start a project, ask a question or get support.

Talk to us →
Company

About Incipit

Who Incipit is, how it works and how to reach it.

Talk to us →
Company

Careers & hiring

Hiring through Incipit and working at Incipit.

Talk to us →
Company

Trust & legal

Policies, security and technical pages.

Talk to us →
Software Development

Web Application Development

A spreadsheet, a shared inbox or an old tool is carrying a process that now needs users, permissions, records and reporting.

The approach

How we work on it

  1. Map the workflow, the user roles and the data before choosing screens.
  2. Build on ASP.NET MVC, C# and SQL Server, with Entity Framework for data access.
  3. Separate public, client and administrative areas with role-based access.
  4. Deliver in reviewable milestones and test each one.

What you receive

Typical deliverables

  • Working application with sign-in and roles
  • Database schema and migration scripts
  • Admin screens and reports agreed in the proposal
  • Deployment and handover notes

What we will and will not promise

Scope, timeline and price are set after discovery; we do not publish fixed packages for applications.

How an engagement runs

Discover, propose, deliver, support

The same four stages apply to every Incipit practice, so you always know what has been agreed and what happens next.

  1. 01

    Discover

    We learn the business need, the people who will use the result and the constraints, before any solution is proposed.

  2. 02

    Propose

    Scope, milestones, responsibilities and ownership are agreed in a written proposal.

  3. 03

    Deliver

    Work is built in milestones. You review working builds and approve each stage before the next begins.

  4. 04

    Support

    Handover of code and documentation as agreed, with maintenance and support available afterwards.

Technology

What we build with

  • ASP.NET MVC
  • C#
  • Entity Framework
  • SQL Server
  • Microsoft Azure
  • Android (Kotlin)
  • Bootstrap

Questions

Before you enquire

Usually yes. We review the code and database first and tell you whether to extend, modernise or replace.

Ownership and handover are agreed in writing at the start of the project.

Related work

Where Incipit has done this

Related services

Describe what you need

Tell us the requirement and your time zone. We reply with questions, options and a written proposal.