Skip to content
Mayrian
pipeline.loop
PlanCodeBuildTestReleaseDeployOperateMonitor

Releases are small and frequent; feature flags separate deploy from release.

LaunchDarkly, Unleash

mayrian.com/team
Two engineers reviewing code together on a laptop in a busy office

How to get started

Three steps to a plan for your software

  1. 1Tell us what you needUse the project form or book a call. A few sentences about the goal is enough to start.
  2. 2Free technical consultationWe go through your goals, users, existing systems and constraints with you.
  3. 3Your planA detailed plan covering the right tech stack, architecture, timeline and budget. Then you decide.

Common challenges

Challenges we solve

Recognise one of these? The capabilities below address each of them.

  • Packaged software forces workarounds

    Core processes run through spreadsheets and manual steps because off-the-shelf software doesn't fit how the business actually works.

  • A legacy system nobody wants to touch

    Critical logic lives in an ageing codebase with few tests and little documentation, so every change is slow and risky.

  • Systems that can't talk to each other

    Data is re-keyed between applications because there are no APIs, or the ones that exist are undocumented.

  • Releases that break things

    Without automated tests and a CI/CD pipeline, each release needs long manual checks and still ships regressions.

What we deliver

Six capabilities, one team

Each capability has its own page with how it works, what you receive and how to start.

Not sure which one you need?

Describe what you want to do and the right capability appears.

mayrian --help

Usage: mayrian <command>

Commands:

$ mayrian new-product

Software development

A product team takes it from discovery to a first release, then grows it sprint by sprint.

requires:

  • ✓ A clear problem and the users who have it
  • ✓ Someone who can make product decisions

Or press Ctrl K on a capability page to switch between them.

How we approach Custom Software Development

We specialize in building bespoke software that prioritizes speed, reliability and scalability. In a volatile, competitive market, we build products with long-term business value: tailored to your processes and ready for future requirements.

With a legacy of reliability, we've earned our clients' trust through consistent delivery of innovative solutions, and we keep pushing boundaries to craft software that transforms businesses.

How we work together

Engagement models

Four ways to work with us, and who carries which risk. Answer three questions to see which fits.

Which model fits?

Can the scope be written down in full today?

Who will manage the engineers day to day?

How long will the work run?

Our suggestionTime and materialsProducts whose scope will change as you learn from users.

Many projects combine models: a fixed-scope discovery, then a dedicated team for the build.

modelFixed scopeSuggestedTime and materialsDedicated teamTeam augmentation
Billed onAn agreed price for an agreed scopeThe time the team actually spendsA monthly fee for a stable, cross-functional teamA monthly fee per engineer
Scope risk carried byUsYouSharedYou
Team managed byUsUs, with your product ownerUs, with your product ownerYou
Changing prioritiesThrough change requestsReprioritise every sprintThe backlog is yours to reorderYour process, your priorities
Usual lengthWeeks to a few monthsAny lengthUsually six months or moreFrom a few months
FitsA discovery, a proof of concept or an MVP whose scope can be written down in full.Products whose scope will change as you learn from users.Long-running product development with a roadmap rather than a fixed scope.Adding specific skills or capacity to a team you already run.

How the work runs

Discovery, alpha, beta, live

Each phase ends with a decision, so you commit to the next only when the evidence supports it.

Understand the problem before building anything.

No production code

what happens

  • User research with the people who'll use it
  • Mapping the current process, systems and data
  • Constraints: policy, technical and legal
  • The riskiest assumptions, listed

what you receive

  • Prioritised user needs
  • Findings on the current process
  • Recommended scope for alpha
  • A cost and timeline estimate

decision · Is there a problem worth solving, and should alpha go ahead?

Two-week sprints in alpha and beta

Planning, a daily stand-up, a review with a demo and a retrospective. Move the cards to see the burndown.

To do 7 pts

In progress 5 pts

In review 3 pts

Done 5 pts

Sprint burndown15 of 20 pts left

Click a card to move it along. Sprint goal: book a check-up as a guest, end to end. Review and retrospective close each two-week sprint.

Where are you today?

Where your software delivery stands

Answer five questions about how you ship software to see what to improve first, and how we'd help.

Change lead time
Change lead timethroughputconstraint

How long from a change being committed to it running in production?

Deployment frequency
Deployment frequencythroughput

How often do you deploy to production?

Failed deployment recovery time
Failed deployment recovery timethroughput

When a deployment fails, how long does it take to recover?

Change fail rate
Change fail rateinstability

What share of deployments need immediate intervention, such as a fix or rollback?

Deployment rework rate
Deployment rework rateinstability

What share of deployments are unplanned, made to fix an incident in production?

throughput →stability →

Work on this first

Change lead time

What we'd put in place:

  • Working in small batches
  • Trunk-based development
  • Streamlining change approval
Software development

Quality you can check

Definition of done

The checks every release we ship passes. Open a check to see what it covers.

All checks have passed14 checks, required on every release

Security

  • Security requirements verified against the Application Security Verification Standard; choose the level below.

    Most business applications, and any that handle personal or commercial data.

Testing

Accessibility

Delivery

Operations

Ownership

What you receive

All of it in your name, from day one.

  • Requirements, user stories and a technical architecture
  • Web, mobile and API code, built in iterations with regular demos
  • Automated unit, integration and end-to-end tests
  • A CI/CD pipeline and repeatable environments
  • API documentation for every integration
  • Ownership and documentation handover, training and support

Technologies and standards

Our technology radar

What we recommend today, and what we'd move away from. Choose a blip to see why.

Adopt Trial Assess Caution
AdoptTrialAssessCautionTechniquesPlatformsToolsLanguages & frameworks

techniques / adopt

Trunk-based development

Short-lived branches merged to main at least daily, so changes reach production in small, low-risk steps.

Our default. We use it on client projects unless there's a reason not to.

Our recommendations. Updated September 2026.

Web and back end

  • TypeScript
  • React
  • Next.js
  • Node.js
  • Python
  • .NET
  • Java

Mobile

  • Swift (iOS)
  • Kotlin (Android)
  • React Native
  • Flutter

Cloud and delivery

  • AWS
  • Microsoft Azure
  • Google Cloud
  • Docker
  • Kubernetes
  • GitHub Actions

Built to

  • OWASP Top 10:2025
  • OWASP ASVS 5.0
  • OpenAPI 3.2
  • WCAG 2.2 AA

How to start

From first call to production

Start where you are. Each step ends with a decision, so you commit to the next one only when it makes sense.

git log --oneline --decorate

git show v0.1

Free technical consultation

Talk through the goal, the users, the systems involved and any deadlines.

  • + A clear view of scope and priorities
  • + A recommended next step
  • + A plan covering stack, architecture, timeline and budget
Book the consultation

By industry

Where it applies

What custom software builds in each industry we serve.

Questions

Common questions
about Custom Software Development

Should we build custom software or buy an off-the-shelf product?

We give you that assessment in the free technical consultation: we recommend a packaged product when it covers the process through configuration, and a custom build when the process is what differentiates you or the workarounds cost more than building.

Native or cross-platform for our mobile app?

We build both, and recommend one for your app. Native apps in Swift and Kotlin get full access to platform features; cross-platform apps in React Native or Flutter share most code between iOS and Android, lowering build and maintenance cost.

Can a legacy system be modernized without a big-bang rewrite?

Yes. We replace the old system part by part behind a routing layer (the strangler fig pattern), so it keeps running until each part has been replaced.

What do we receive at the end of the project?

Our delivery process ends with ownership and documentation handover, followed by training and support, so your team can run and extend what we built.

How is a project priced?

Well-defined scopes are delivered as fixed-price engagements; when requirements are still evolving, we provide a dedicated team instead. Either way, the free technical consultation ends with a plan covering tech stack, architecture, timeline and budget, so you know the cost before work starts.