Illinois LLC · Chicago · Est. 2026
Software that survives production
the only environment whose opinion counts
Logitex Development is a two-founder engineering studio. We design, build and operate custom web, mobile and cloud systems for companies that need the thing to work on Monday morning — not to demo well on a Friday.
- Entity
- Illinois LLC
- Base
- Chicago, IL
- Team
- Senior only
- Handover
- Code + runbook
- Typed end to end
- Migrations in version control
- Staging URL from day one
- Written scope before code
- Your repository, your keys
- Backups restored on a schedule
Capabilities
What we build
Six things, done properly, instead of a list that covers every acronym in the market. If a project needs something outside this sheet, we say so and point you at someone who does it every day.
·
What that means in practice
Tools
WEB
Web platforms
Customer portals, dashboards and marketing sites built on the App Router. Server-rendered where it matters, typed from the database to the button.
- Next.js
- TypeScript
- PostgreSQL
- Tailwind
APP
Mobile applications
One React Native codebase for iOS and Android, or native when the hardware demands it. Store submission and release pipeline included.
- React Native
- Expo
- Swift
- Kotlin
SYS
Custom business systems
CRM, ERP, field service, internal tooling. The software your operation runs on, shaped to how you actually work instead of a rented workflow you have to bend around.
- Node.js
- Queues
- RBAC
- Audit logs
OPS
Cloud & DevOps
Infrastructure as code, CI/CD, observability and a monthly cost you can predict. Handover includes the runbook and the on-call escalation path.
- AWS
- Terraform
- Docker
- GitHub Actions
API
Integrations & APIs
Payments, ERP, logistics, and the legacy SOAP endpoint nobody wants to touch. We make two systems that were never meant to meet agree on a contract.
- OpenAPI
- GraphQL
- Webhooks
- Stripe
DSN
Design systems & audit
Interface design delivered as tokens and components, not flat mockups. Every launch is preceded by a security, performance and accessibility pass.
- Figma
- Design tokens
- OWASP ASVS
- WCAG 2.2
How a Logitex system is put together
Four layers, one contract each
We build in separable layers, each with a defined boundary and one contract. This is that idea as an object — scroll to take it apart.
- L4
Interface
Server components, design tokens, no client JavaScript unless the interaction needs it. Ships as static HTML wherever the content allows.
- L3
Contracts
One typed API boundary, validated at the edge and shared by web and mobile. If the schema changes, both clients fail to compile — not in production.
- L2
Services
Business logic in isolated modules with explicit dependencies. Anything slow goes on a queue, and every job is idempotent by default.
- L1
Data
PostgreSQL with migrations in version control and a restore rehearsed on a schedule, not trusted on faith.
Register
The tools we keep sharp
Deliberately short. We would rather be excellent with a small set than adequate with everything, and we will tell you when your problem calls for something we do not run.
- Interface
- TypeScriptReact 19Next.js 16Tailwind CSSReact Nativethree.jsGSAP
- Services
- Node.jsNestJStRPCGraphQLPythonGoREST + OpenAPI
- Data
- PostgreSQLPrismaRedisClickHouseS3Elasticsearch
- Infrastructure
- AWSVercelDockerTerraformGitHub ActionsCloudflare
- Quality
- PlaywrightVitestSentryGrafanaOWASP ASVSWCAG 2.2 AA
Process
Six phases, visible from the first week
You get a staging URL in week one and a written decision record for every architectural choice. No phase starts before the previous one is signed off.
$
- 01▸discovery[1–2 weeks]
- 02scope workshops · 3 sessions with your team
- 03success criteria written down and agreed
- 04fixed-price estimate issued
- 05▸architecture[1 week]
- 06data model + API contract drafted
- 07decision records (ADR) you keep after handover
- 08threat model and access roles defined
- 09▸build[4–16 weeks]
- 10two-week increments, demo at the end of each
- 11staging URL live from day one
- 12code review on every pull request
- 13▸hardening[1–2 weeks]
- 14end-to-end suite green on real devices
- 15security audit against OWASP ASVS
- 16load test, then accessibility pass to WCAG 2.2 AA
- 17▸launch[2–4 days]
- 18pipeline, DNS and certificates cut over
- 19monitoring, alerts and error tracking armed
- 20runbook + credentials handed to your team
- 21▸operate[ongoing]
- 22response time fixed by the SLA you signed
- 23patches, dependency upgrades, backup drills
- 24monthly report: uptime, cost, what changed
- 25— delivery pipeline complete
System blueprints
How we would build it
Logitex was founded in 2026, so there is no client wall here yet. Instead: three reference designs, written the way we write a real architecture proposal, so you can judge the engineering rather than a logo grid.
Reference design produced in-house. Not a delivered client project.
- 01BlueprintConstruction & trades
Field service CRM
Dispatch, job sheets and invoicing for a company running 40 crews across three states, with half the workforce offline half the day.
- React Native
- Expo
- Node.js
- PostgreSQL
- 02BlueprintRetail & D2C
Headless commerce platform
A storefront for 12,000 SKUs and four markets that has to stay fast during a campaign spike and keep the ERP as the single source of stock.
- Next.js
- TypeScript
- PostgreSQL
- Elasticsearch
- 03BlueprintHealthcare
Patient portal
Appointment booking, results and secure messaging for a clinic group, designed against HIPAA technical safeguards from the first schema.
- Next.js
- Node.js
- PostgreSQL
- FHIR
The studio
Two founders, no layer between you and the engineer
Logitex Development LLC is an Illinois company. It is deliberately small: the people who scope your project are the people who build it, and there is no account manager relaying a message between you and the person typing.
What we hold to
01Your repository from day one
Code lands in an organisation you own. IP assigns to you on final payment, in writing, in the master agreement.
02Estimates in writing or not at all
No number over the phone. A scope document and an estimate, and if the scope moves, a change order before work continues.
03We say no to work we would do badly
Outside the six disciplines on our capability sheet, you get a referral instead of a learning curve on your budget.
04Handover is a deliverable
Runbook, architecture notes, credentials and a walkthrough. A project is finished when your team can operate it without us.
Company record
- Legal name
- Logitex Development LLC
- Entity type
- Limited liability company
- Jurisdiction
- Illinois, United States
- Registered office
- Chicago, Illinois
- Founded
- 2026
- Governance
- Two managing members
legal@logitexdevelopment.com
Notes
What we learned, written down
Short pieces from the actual work: a failure worth documenting, a decision worth explaining, a rule we now apply by default. No thought leadership, no reheated release notes.
August 13, 2026
The font that 500'd every route in dev, and not in production
A next/font configuration that the production build was perfectly happy with took down every route in development. Where the two diverge, and why a test suite that only exercises the build cannot see it.
6 min readNext.jsTurbopackDebugging
August 5, 2026
Decide the conflict rules before you write the offline app
Offline-first field applications do not fail in the sync code. They fail because nobody wrote down what happens when two people edit the same job, and the answer gets invented at three in the morning by whoever is on call.
7 min readArchitectureMobileField service
July 28, 2026
This site has no cookie banner, because it has no cookies
The language switcher is where the first cookie usually sneaks into a marketing site. Putting the locale in the URL removes the cookie, the banner and an SEO problem in one move.
3 min readPrivacySEOi18n
Straight answers
Before you send the first email
Who actually writes the code?
The two founders. For a defined piece outside our disciplines — a motion designer, a compliance reviewer — we bring in a specialist, and you are told who they are and what they own before they start.
Do we own what you build?
Yes. Repositories are in your organisation from the first commit, and intellectual property assigns to you on final payment under the master services agreement. No licence-back, no hostage clause.
How do you estimate a project?
A short discovery phase produces a written scope, then a fixed estimate against it. Discovery is paid and small; if you take the scope elsewhere afterwards, the document is yours.
What happens when the scope changes?
It gets a change order: what changes, what it costs, what it does to the date. Signed before work continues. This is the single most common reason projects go sour, so we make it boring paperwork instead of an argument.
Where are you, and when can we talk?
Logitex Development LLC is registered in Illinois and the team works across US Central and Central European hours. That gives a real daily overlap window rather than an answer tomorrow.
Will you take over a system someone else built?
Often, yes. It starts with a paid audit: what state the code is in, what it costs to run, what has to change first. If the honest answer is a rewrite, we say so with the numbers attached.
Have a system like this in mind?
Send us the shape of the problem. You get a written scope and a fixed number before anyone writes code.