Start a Project

Custom Software Development

Business management systems, internal tools, and portals designed around how your team actually works.

A laptop showing the Procura purchase approvals concept, with a queue of requests and the details of one request awaiting approval. An HMTZ Lab concept with sample data.
Procura, a fictional HMTZ Lab concept. See application concepts

Software that fits your operations, not the other way around

Many organizations run on spreadsheets, email threads, and tools that almost fit. Custom software replaces them with one system designed for your workflows: requests, schedules, records, bookings, and reports.

Projects range from a single internal tool to multi-location platforms with portals and integrations. HMTZ Tech is based in Minneapolis and builds software for organizations in Minnesota and across the United States.

Signs a process has outgrown its tools

  • Scattered spreadsheets

    Several versions of the same list, and nobody is sure which is current.

  • Manual scheduling

    Appointments, shifts, or jobs are arranged by phone and message, then copied into a calendar.

  • Repetitive admin

    The same details are typed into several places every day.

  • Requests that slip through

    There is no single place to see what is open, who owns it, and what is overdue.

  • Disconnected records

    Customer and staff information sits in different tools, so simple questions take several searches.

  • Limited visibility

    Managers cannot see the day’s work or the week’s workload without asking around.

What custom software can look like

Illustrative HMTZ Lab concepts with fictional businesses and sample data. They are not existing products or client projects; a real system is shaped by your requirements.

A desktop monitor and a phone showing the Corelane operations dashboard concept: open orders, requests, completion rates, a weekly throughput chart, and work in progress.
Concept · HMTZ Lab

Business management systems

The problem. Orders, requests, and staff updates are spread across spreadsheets and inboxes, so nobody has the full picture of the day.

Could include

  • An overview of open work and its status
  • Orders, jobs, or requests in one list
  • Reports for managers
  • A phone view for staff away from the desk

How it fits. Can replace the spreadsheets first, then connect to accounting or the website form in a later phase.

See Business Management Systems

A laptop showing a weekly staff schedule concept with color-coded shifts, and a phone showing one employee’s upcoming shifts.
Concept · HMTZ Lab

Employee and scheduling management

The problem. Rotas change often, and staff hear about last-minute changes too late or not at all.

Could include

  • Weekly rotas by location or team
  • Time-off and swap requests with approval
  • Coverage and hours at a glance
  • Personal schedules on each phone

How it fits. Built around your roles, locations, and approval rules rather than a generic template.

A browser window showing a client management concept: a list of clients with stages and a profile panel with recent activity and open tasks.
Concept · HMTZ Lab

Customer and client management

The problem. Customer details and history live in personal inboxes, so it is hard to see where each relationship stands.

Could include

  • Client records with contacts and stage
  • An activity timeline and notes
  • Tasks and follow-ups with owners
  • Search and filters for the team

How it fits. Can import existing customer lists and, where supported, receive new inquiries from your website.

A dark browser window showing the Archivo document library concept: collections, a file list with statuses and owners, and a document preview with version and access details.
Concept · HMTZ Lab

Document and records management

The problem. Contracts, policies, and invoices sit in shared drives with unclear versions and no record of who can see what.

Could include

  • Collections with access levels
  • Versions and review dates
  • Statuses such as awaiting signature
  • Search by client, type, or tag

How it fits. Designed around your filing structure and approval steps. Security, retention, and access rules are defined during discovery.

A laptop showing the Teamroom project workspace concept with a timeline, and a phone showing the Harborview resident portal concept with rent due, quick actions, and maintenance requests.
Concept · HMTZ Lab

Custom web applications and portals

The problem. Customers or staff need a secure place to see and update what concerns them, and off-the-shelf tools do not fit the process.

Could include

  • Sign-in with roles for customers or staff
  • Requests, approvals, and notifications
  • Timelines and shared files
  • Works in the browser on any device

How it fits. Portals can sit alongside your website and internal systems. Sign-in, data protection, and integrations are scoped for each project.

Why scope matters: features, security requirements, integrations, and architecture are confirmed through a requirements review, so the proposal reflects what your organization actually needs. Nothing is guaranteed until it is agreed in writing.

How a software project runs

Projects vary in size and complexity, but each follows the same path.

  1. Discovery

    A requirements review of how the work is done today and what the system must do.

  2. Planning

    Priorities, scope, and technical approach agreed and confirmed in a proposal.

  3. Development

    The system is built in stages, with reviews at agreed points.

  4. Testing

    Checked against the agreed requirements on the devices and browsers your team uses.

  5. Handover

    Launch and handover as set out in your project agreement.

Runs in the browser, on any device

  • Desktop and mobile

    Systems are built as web applications that work on computers, tablets, and phones.

  • No app store required

    People open the system in their browser. We do not build native App Store or Google Play apps.

  • Access by role

    Office staff, field teams, or customers each see what is relevant to them, as agreed for the project.

It starts with a requirements review

Before pricing a software project, we look at how the work is done today: who is involved, what information moves where, and which tools are already in use.

Together we decide what the system must do first, what can wait, and what it needs to connect to. That is what the proposal and price are based on, so complex features are understood before they are quoted.

More software concepts

See four business management system concepts in the Showcase, alongside custom web applications and portals.

View Business Management Systems

Connecting tools rather than building new?

If your current software works but your systems do not share information, integrations and automation may be the better fit.

Explore Business Automation & Integrations

Software tiers

Indicative one-time ranges. The final price follows the requirements review.

Small Internal Tool

One clearly defined business need.

$1,500–$3,500one-time

  • Simple request tracker
  • Basic inventory tracker
  • Internal scheduling tool
  • Simple workflow dashboard
Start a Project

Business Management System

A system that runs a core part of your operations.

$3,500–$8,000one-time

  • Customer management
  • Staff scheduling
  • Booking management
  • Basic reporting
  • Internal dashboards
Start a Project

Advanced Business Platform

Connected workflows across teams, locations, or customers.

$8,000–$18,000one-time

  • Customer portals
  • Multi-location management
  • Connected workflows
  • Advanced operational dashboards
  • Multiple integrations
Start a Project

Complex Projects — Custom Quote

Larger or unusual systems, evaluated individually.

$18,000+one-time

  • Scope defined through a requirements review
  • Priced after evaluation
Start a Project

Which tier? A Small Internal Tool handles one clearly defined task. A Business Management System runs a core part of your operations. An Advanced Business Platform connects several teams, locations, or customer groups. Complex Projects are assessed individually.

Full custom software pricing, notes, and exclusions

Hosting and ownership

  • Hosting, database, storage, and third-party service fees are normally paid by you. We can set them up or manage them under a separate agreement.
  • Support and maintenance for software are agreed per project. Website care plans do not cover software.
  • Ownership, licensing, and reusable components are defined in each project agreement.
  • We do not claim regulated-industry compliance or security accreditation. Projects involving sensitive data need separate legal, privacy, and security review.

Looking ahead, HMTZ Tech plans to develop its own subscription software products. None is available yet, and client software is not turned into HMTZ Tech products.

Industries we work with

Sectors where this service is often a good fit. No client relationships are implied.

Frequently asked questions

Common questions about custom software development.

How is a software project priced?

The tiers on the Pricing page give indicative ranges. Final pricing follows a requirements review, and complex features are never guaranteed at a fixed price.

Can you connect the tools we already use?

Often, yes. Integrations and automation are scoped as part of the project and priced within the software ranges or by quote. See Business Automation & Integrations for details.

Who pays for hosting and databases?

Hosting, database, storage, and third-party service fees are normally paid by you. HMTZ Tech can configure or manage them under a separate agreement.

Do care plans cover custom software?

No. Website care plans apply to websites. Support and maintenance for custom software are quoted per project.

Who owns the software?

Ownership and licensing are defined clearly in each project agreement.

Will it work on our phones?

Yes. Systems are web applications that work in the browser on phones, tablets, and computers. We do not build native App Store or Google Play apps.

Do you sell ready-made software?

Not yet. We currently build software for individual clients. Our own products are planned for the future.

Starts with your workflow

Has a process outgrown its spreadsheet?

Walk us through how the work is done today.

Start a Project