Hesvian Labs

Your next system. Built asynchronously.

Start a project

Custom software

Custom business software and SaaS development, built around how you work.

Internal tools, customer portals and software products designed from your process, delivered in milestones you can test and handed over with code and documentation your team can build on.

When custom software is the right answer

  • Spreadsheets doing the job of a system

    A business process living in shared spreadsheets, with versions, permissions and errors nobody controls.

  • Off-the-shelf tools that almost fit

    Workarounds, duplicated data and features you pay for but cannot adapt to how your team works.

  • A product idea that needs a first version

    A SaaS or customer-facing product that needs a focused first release to test with real users.

  • Legacy software that blocks change

    An internal application that is hard to modify, undocumented or understood by only one person.

What we build

  • Internal tools and back offices

    Admin panels, approval flows, dashboards and operational tools for your team.

  • Customer portals

    Secure areas where clients follow orders, documents, requests or projects without emailing for updates.

  • SaaS products and MVPs

    A first version scoped to the core problem, with accounts, the essential workflows and the integrations needed to learn from real users.

  • Connected data and reporting

    One source of truth for data that now lives in several tools, with the reports people actually use.

  • Modernization

    Gradual replacement of legacy parts while the business keeps running.

  • AI features where they add value

    Search, summaries, extraction or assistants built into the product, with the same tests as any other feature.

Built to be maintained

What every project includes
  • Roles and permissions
  • Audit history
  • Automated tests
  • Written documentation
How it is built
  • Web applications
  • APIs and integrations
  • Relational databases
  • Hosting in your own accounts

We use mainstream, well-documented technology chosen per project, so any competent team can maintain it later.

How a project runs

Software projects start with a Clarity Sprint to agree scope, architecture and priorities. Delivery follows in milestones, with recorded demos and written approvals.

  1. 01

    Clarity Sprint

    Project fee $4,500

    An audit of how the work happens today and a decision-ready system plan.

  2. 02

    System Delivery

    From $20,000

    The software, AI capabilities and integrations defined in the blueprint, delivered in clear milestones.

  3. 03

    Continuous Evolution

    From $2,000

    Ongoing improvements with agreed capacity, once the system is live.

All prices in USD, including applicable taxes. Each stage is scoped and approved separately. Pricing and what each stage includes

How we keep scope honest

  • A first version is deliberately small

    We scope the smallest version that solves the core problem. Everything else is a decision for later, not hidden scope.

  • Quotes follow an agreed scope

    System Delivery is quoted against a written scope. Changes are estimated and approved in writing before work starts.

  • Hosting and third-party fees are separate

    Cloud hosting, domains, software subscriptions and usage-based services are paid to their providers.

  • Regulated work needs more

    Projects in regulated sectors or with sensitive data need a separate assessment of security and compliance requirements.

Example: replacing a project-tracking spreadsheet

Illustrative scenario — not a client project

An engineering services firm tracks client projects in a shared spreadsheet: statuses, hours, documents and invoices. Mistakes appear when two people edit the same row, and clients ask for updates by email.

  1. Map the data, the roles and the questions people ask the spreadsheet.
  2. Build an internal tool with roles and change history, importing the existing data.
  3. Add a client portal where each client sees only their projects and documents.
  4. Connect invoicing and retire the spreadsheet once the team has used the tool for a full cycle.

The aim would be one reliable source of truth and fewer status emails, with a first release that covers only the essentials.

Questions

  • Who owns the code?

    Ownership and licensing are agreed in writing before work starts. The handoff includes the code, the documentation and the access your team needs to run and change the system.

  • Can you build a SaaS MVP?

    Yes. We scope a first version around the core problem, with accounts, the essential workflows and the integrations needed to test it with real users.

  • Can you work with our developers?

    Yes. We can work alongside your team, with written decisions, reviewed code changes and shared repositories.

  • How long does it take?

    It depends on scope. The Clarity Sprint produces the scope, milestones and an estimate before you commit to delivery.

Start with one process your team repeats.

Describe a process that takes too much manual work. You’ll get a straight answer on what can be automated, what needs custom software and what is better left as it is.