Devtrox
What we do

Six practices.
One team that
actually shows up.

We don't have a "talent pool" you'll get assigned. Every engagement is staffed from the same people you'll meet on day one — designers and engineers who pair as a single unit and care about each other's craft.

01 — Practice

Custom software

Web platforms, internal tools, and bespoke product surfaces — built to outlive the trend cycle. We write boring code that lasts.

TypeScriptNext.jsPostgrestRPCElixir
i.Discovery sprint

Two weeks of interviews, prototype, and a written strategy memo.

ii.Foundation build

Architecture, schema, design system, and the first vertical slice.

iii.Iteration runway

Weekly demos, paired engineering, and prod-quality from week one.

iv.Handover & aftercare

Documentation, runbooks, and a 90-day pair-and-fade with your team.

02 — Practice

Mobile apps

iOS and Android products that earn their permanent slot on the home screen. Native by default, Flutter when it earns its keep.

SwiftKotlinSwiftUIComposeFlutter
i.Concept & flows

Hand-drawn first, Figma second. We design for the thumb.

ii.Native scaffolding

Modular architecture, offline-first, deep linking, push.

iii.Beta & telemetry

TestFlight cohorts and a private telemetry pipeline you own.

iv.Store launch

Listing, screenshots, app preview videos, and rollouts.

03 — Practice

Cloud & DevOps

Quiet, boring, predictable infrastructure. Our goal is for you to never have to think about us — or your servers — at 2am.

Terraformk8sAWSGCPDatadog
i.Platform audit

A two-week reading of what you have and what hurts.

ii.Migration plan

Step by step, with explicit rollback paths at every gate.

iii.Observability

SLOs, dashboards, and on-call runbooks your team owns.

iv.Cost & calm

A monthly review until the bill stops surprising anyone.

04 — Practice

Applied AI & ML

LLM and ML systems wired into the messy reality of your workflows. No magic. Lots of evals. A clear off-ramp if it stops earning its place.

PythonPyTorchLangChainpgvectorModal
i.Problem framing

Where can ML actually move a number you care about?

ii.Evals first

A test set before a model. A scorecard before a launch.

iii.Production wiring

Streaming, caching, fallbacks, and PII boundaries done properly.

iv.Quiet retraining

Drift monitoring and a calendar for revisiting model choice.

05 — Practice

UI / UX design

Interfaces that feel inevitable. Typography, motion, and information density treated as first-class engineering problems.

FigmaFramerWebflowOrigami
i.Research

Five interviews and a wall of competitor screenshots, every time.

ii.Design system

Tokens, components, and the prose that explains them.

iii.Surface design

Flows shipped as Figma, then immediately as HTML.

iv.Brand voice

Microcopy, empty states, and the things only readers notice.

06 — Practice

Product consulting

When the answer isn't more code. Strategy reviews, team coaching, and the rare art of saying no.

StrategyRoadmapsCoachingHiring
i.Three-week diagnostic

Interviews, reading, and a 20-page memo with three sharp options.

ii.Quarterly cadence

Two senior partners on retainer, four reviews a year.

iii.Hiring partner

Scorecards, interview kits, and live shadow days.

iv.Coaching

1:1s with new heads of product and engineering.

How we work

A loop, not a waterfall.

01

Listen

Two weeks of interviews, transcripts, and a written memo. We read more than we sketch.

02

Frame

Three sharp options on one page. We pick the one you can actually defend.

03

Build

Weekly demos, prod-quality from week one. Boring tools, sharp opinions.

04

Hand off

A 90-day pair-and-fade with your team. The handover is the deliverable.

Not sure which practice
fits? We'll tell you.

Send a paragraph about what's on your plate. We'll come back with a one-page sketch of how we'd start, usually within two business days.