The facts about Micro Tech: what we do and what proves it.

01

At a glance

Name

Micro Tech

Legal entity

OR Micro Tech

Registered address

Zaima Šarca 14, 71000 Sarajevo, Bosnia and Herzegovina

Based in

Sarajevo, Bosnia and Herzegovina

Shipping production software since

2020

Clients in

US, Germany, Sweden, West Africa

How we work

Remote · 9–18 CET · 4 h overlap with US and EU

Engagements

Project · Long-term · Technical lead embedded in your team · Fixed-price written assessment

Billing

Development is billed by the hour. Only a written assessment has a fixed price, with its scope, the document and the delivery date agreed up front.

Languages

English, Bosnian

Website

www.microtech.consulting

Email

contact@microtech.consulting

A 30-minute call

Book on Calendly

02

What we do and the proof

Each area lists the services we offer in it and the case studies that show the work. An area goes on this list only when at least one case study backs it.

All services, grouped by area →

03

Sectors and markets

Clients are listed by sector and market. We don’t name them.

Logistics: a US marketplace for truck services

• Four years rebuilding a live US marketplace
• Live analytics with annual reports in under a second
• Event tracking from listing position to phone call
• Scheduled jobs that ran renewals and recurring billing
• One codebase for five kinds of user
• Code standards enforced first, then AI in daily use

Regulated finance: remote KYC in Germany

• Remote identity verification that holds up in review
• Passport chips and payment terminals in React Native

Government: identity documents in West Africa

• Passport applications taken where there is no network
• An AWS bill eight times larger than it needed to be

Cross-border remittance and POS terminals

• Passport chips and payment terminals in React Native
• Payment integrations for five products in four markets
• Frozen invoices and offline coupons that pay out once

Healthcare and finance: meetings under HIPAA

• A file permission graph for a meeting platform

Construction: ERP and white-label estimating software

• A construction ERP that tracks stock down to the shelf
• A design system for 30+ white-label brands

Retail data: BI reporting for a US-market supplier

• A 15-minute report now opens in 0.2 seconds

B2B SaaS: a Swedish code-analysis company

• A HubSpot site marketing edits without a developer

04

Technologies in the case studies

The list covers every technology named in a case study’s stack, grouped by area. Technologies used in three or more case studies are highlighted. Open one to see which case studies used it.

Web and frontend

• Next.js
• React
• CSS
• JavaScript
• TypeScript
• Fabric.js
• HubL
• HubSpot CMS
• Redux
• SCSS
• styled-components
• Vite

Mobile and hardware

• React Native
• Android
• Expo
• Kotlin
• NFC / ICAO 9303
• biometrics
• Java
• offline-first
• Swift
• Turbo Modules

Backend

• Node.js
• WebRTC
• Express
• Handlebars
• NestJS
• WebSockets

Databases and data

• MySQL
• InfluxDB
• PostgreSQL
• Amazon Redshift
• materialized views
• Neo4j
• OpenSearch
• Redis

Cloud

• AWS
• S3
• AWS Lambda
• AWS Transcribe
• SQS

Payments and integrations

• Apple Pay
• DocuSign
• Google Pay
• national gateways
• PayPal
• SAP
• Stripe

AI and machine learning

• Claude Code
• Figma MCP
• TensorFlow

Design and tooling

• Figma
• CI
• custom ESLint plugin
• design tokens
• ESLint
• npm
• pnpm workspaces
• pre-commit hooks
• Turborepo

05

What we don’t do

Projects that conflict with our values

We have turned down projects for this reason.

Rewrites for their own sake

We stabilize first and rewrite only when it is worth the cost.

Estimates presented as measurements

For example, the ~50% increase in team throughput once standards were checked in CI is marked as an estimate.

Client names

We describe engagements by sector and market and never name the client.

06

How to read the evidence

• On the home page and the case study and services indexes, the label on a figure says how we know it: Measured, Counted, Derived or Estimate. Other labels, such as Constraint or Outcome, say what kind of figure it is.
• On the services page, a service that no case study fully backs is marked Partial proof. Its evidence comes from related client work, our own products or our articles.
• Case studies are written by the person who did the work. They say “I” for the author’s own work and “we” where a team worked.
• Every case study except 01 has the same five parts: the summary, the constraint the work had to respect, what was done, the result, and what the author would do differently. Case study 01, on the CDS design system, is built around the five problems the system solves.

07

Contact, profiles and files

Contact

• contact@microtech.consulting
• The contact form

Profiles linked from this site

• LinkedIn
• GitHub
• Upwork

For search engines and AI assistants

• llms.txt: A map of the site for language models
• llms-full.txt: The company facts, every case study and every service in full, in one text file
• sitemap.xml: Every page, in both languages
• feed.xml: New articles, as RSS