TekisHub
Contact us

Build

Custom Applications

Web and enterprise applications designed, built and rolled out by our own engineers, from a first release to a system your company runs on.

Start a project See examples
Sticky notes on a planning board
First release
8–12 weeks for most products
Typical team
4–8 people, one delivery lead
Sprints
Two weeks, demo at the end of each
You own
All code, designs and documentation

Overview

Web and Enterprise Systems Built Around How You Work.

Off-the-shelf software rarely fits how a business actually works. We build applications around your processes, data and users, so teams stop working around their tools.

Every project starts with discovery: who uses the system, what it needs to do, and what it has to connect to. We then build in short iterations, with working software to review every two weeks.

You Might Need This If…

  • Work runs on spreadsheets, email and copy-paste between systems.
  • An off-the-shelf product covers 70% of what you need and the rest is workarounds.
  • A legacy system is hard to change and only one or two people understand it.
  • Customers or partners phone or email for things they could do themselves online.
  • You have a product idea and need a team to build it properly.

What we deliver

Custom Applications Services

Take one piece or the whole scope, delivered by one team.

  • Line-of-Business Systems

    Applications for operations, finance, HR and field teams that replace spreadsheets and manual steps.

  • Customer and Partner Portals

    Secure self-service portals for ordering, account management, onboarding and support.

  • Workflow and Approvals

    Digital forms, approvals and audit trails for processes that still run on email.

  • Integration

    APIs and middleware that connect new applications with ERP, CRM and other systems already in place.

  • Modernization

    Rebuilding or re-platforming legacy applications without losing the business rules inside them.

  • Rollout and Training

    Phased go-lives, data migration, user training and documentation.

What good looks like

The Outcomes We Work Towards

We agree how success will be measured before work starts, and report against it.

  • Software people choose to useDesigned with the people who do the work, tested with them before it ships.
  • Releases you can plan aroundWorking software every two weeks, with a backlog you can see and reorder.
  • A system you can maintainClean code, automated tests and documentation your team can pick up.

How we work

Four Phases, with Clear Deliverables

Each phase ends with something you can review and sign off, so you can stop, change course or continue with confidence.

  1. 12–3 weeks

    Discover

    Workshops with your users to map processes, requirements and constraints.

    You get

    • User and process interviews
    • Prioritized feature list
    • Risks and assumptions log
  2. 22–4 weeks

    Design

    Architecture, data model and clickable prototypes agreed before build starts.

    You get

    • Clickable prototype
    • Architecture and integration plan
    • Release plan and estimate
  3. 3Two-week sprints

    Build in Sprints

    Two-week iterations with a demo of working software at the end of each.

    You get

    • Working features every sprint
    • Automated tests
    • Sprint demo and report
  4. 4Ongoing

    Launch and Support

    Go-live, hypercare and ongoing enhancements under a support agreement.

    You get

    • Go-live and hypercare
    • Training and runbooks
    • Support agreement

Technology

Tools and Platforms We Work With

We choose tools to fit your stack and your team, and we document what we build so you’re never locked in.

  • Java
  • .NET
  • Node.js
  • Python
  • React
  • Angular
  • PostgreSQL
  • SQL Server
  • REST and GraphQL APIs

You see progress the whole way through, in the same kind of view shown here.

Examples

What This Work Looks Like

Two typical engagements: the problem, what we did, the team and the result.

Example scenario · Regional distributor, 400 staff

Replacing Spreadsheets with an Operations Portal

The situation

Orders, stock and delivery schedules were tracked across a dozen shared spreadsheets, with frequent errors and no audit trail.

What we did

  • Mapped the order-to-delivery process with the operations team
  • Built a web portal with role-based screens for sales, warehouse and drivers
  • Integrated it with the existing ERP and accounting system
Team
Delivery lead, business analyst, 3 developers, QA engineer
Timeline
5 months to first release
Result
One place for orders and stock, with every change recorded.

Example scenario · Specialty insurer

Modernizing a Legacy Claims System

The situation

A 15-year-old desktop application was slow to change and its original developers had left.

What we did

  • Documented the existing rules and data model
  • Rebuilt it as a web application in stages, module by module
  • Ran old and new side by side until each module was signed off
Team
Solution architect, 4 developers, business analyst, QA engineer
Timeline
9 months, released in four stages
Result
Changes that used to take months now ship in a sprint.

These examples show the kind of work we do. They are illustrative and do not describe a named client.

Lower Manhattan
United States edition

Building for US Organizations

  • Accessibility to WCAG 2.1 AA, in line with ADA expectations and Section 508 for public bodies.
  • Data handling planned around HIPAA, GLBA or state privacy laws such as the CCPA where they apply.
  • Integrations with the ERP, payroll and tax systems US companies already run.
  • A US-hours delivery lead and architect on every project, with engineering in India for extended hours.

Team and pricing

Who You Work with, and How It’s Priced

Every engagement has a named delivery lead. Need individuals rather than a team? We place full-stack developers, solution architects, business analysts and more on contract, contract-to-hire or direct hire terms.

A Typical Team

Sized to the work; this is a common starting point.

  • Delivery lead1
  • Business analyst1
  • UX designerAs needed
  • Developers2–5
  • QA engineer1
  • Solution architectPart-time

Project

A fixed scope and timeline, led by our delivery lead. Often fixed price for discovery and first release.

Dedicated Team

A stable team working on your backlog and tools, billed monthly. Scale up or down with notice.

Managed Service

We run and improve what has been built, against agreed service levels, for a monthly fee.

Hire full-stack developers instead

FAQs

Questions We Often Hear

Do we own the code?

Yes. You own all code, designs and documentation from day one, kept in your own repositories if you prefer.

Fixed price or time and materials?

Both. We often fix the price of discovery and the first release, then move to a monthly team for what follows.

Which technologies do you use?

Mostly .NET, Java, Node.js and Python on the back end, React or Angular on the front end, on AWS or Azure. We fit your standards where you have them.

Can you work with our in-house developers?

Yes. Many projects are mixed teams, with our engineers following your coding standards and review process.

What happens after go-live?

A period of hypercare, then a support agreement sized to how much change you expect. See Application support for details.

Industries

Industries We Deliver For

More from Build

Related Services

All Build services

Next step

Talk to Us About Custom Applications

Tell us what you need and when. We’ll come back with an approach, a team and a plan.

  1. We reply within one working day.
  2. A short call with someone who knows the subject, not a salesperson reading a script.
  3. A written proposal or shortlist, usually within a week.

Prefer email? Write to info@tekishub.com.

Data Privacy