Discovery
& Scope
We pull the product apart before we build it: who uses it, what it has to do on day one, what it must not do yet. You leave with a scope, a timeline and a number — not a proposal full of maybes.
United States — taking new builds for Q4
WE BUILD the whole STACK. iOS. ANDROID. AI INSIDE.
A full-stack product studio in the United States. We design and ship iOS and Android apps, business software and internal portals — with AI wired in where it moves the numbers, not where it looks good in a deck.
01 — How we work
One team from the first sketch to the app store and the server it talks to
Discovery
Design
& Architecture
Interface and data model get designed together, so the screens and the schema never fight each other. You see clickable flows before a production line of code is written.
Build
Full-Stack
Native-grade iOS and Android, the backend behind them, the admin portal your operations team actually lives in, and the AI layer wired into real data — all by the same people.
Launch
& Iterate
Store submission, rollout, monitoring, and the unglamorous weeks after launch when the product meets real users and has to change. We stay for those.
Build something new
You have a product in your head and nothing in a repository. We take it from scope to a shipped app on both stores, with the backend and the admin side already built in.
Door BPut AI into what you already run
You have a working product or an internal system and a pile of data doing nothing. We integrate the AI layer, rebuild what blocks it, and leave the rest of your stack standing.
02 — Scope engine
Pick what you are building.
Pick what you are building.
See what it takes.
Indicative planning model, not a quote. Timelines move with the complexity of the work — the number of integrations, the state of an existing codebase, data migration, review cycles and any compliance requirements can change them substantially in either direction. Real numbers come out of the discovery phase, where the scope gets fixed in writing.
Discovery
Design
Build
Launch
- Estimated timeline
- 19 wks
- First clickable build
- wk 6
- Surfaces shipped
- 3
- Engagement
- Fixed scope
These figures assume a typical scope at the selected stage. Actual duration depends on the complexity of your product — integrations, data volume and quality, regulatory requirements, the condition of existing code, and how quickly decisions get made on your side. A build can land faster than shown, or materially slower. Nothing here is an offer or a commitment.
03 — Business audit
Before we build anything,
Before we build anything,
we look at how you actually work.
Most companies do not need more software. They need the right three things automated and the rest left alone. So we start by auditing the business itself — the operation, not the wish list.
We sit with the people who do the work, follow a job from the first phone call to the final invoice, and write down every place where a human is moving information that a machine should be moving. Then we tell you which of those are worth fixing, which are not, and what each one is costing you now.
You get the findings whether or not you build with us.
What we look for
-
01
Work done twice
The same information typed into two systems because they do not talk. Email to spreadsheet to accounting package, by hand, every day.
-
02
Waiting
Jobs that sit still because they need someone's approval, someone's answer, or someone to notice an email at all.
-
03
Work that walks out the door
Enquiries nobody answered, calls that came after hours, quotes that took three days when the customer needed one.
-
04
Risk sitting in plain sight
A process that only one person knows. Access nobody revoked. Approvals with no record. A shared spreadsheet holding customer data.
Where automation usually pays — and what it replaces
Calls answered in any language, around the clock
The pain
Calls arrive outside office hours, in languages nobody on shift speaks. They go to voicemail, or they ring out. Nobody can tell you how many you lost last month, because a call that was never answered leaves no record.
What we put in
An AI voice agent answers on the first ring, in the caller's own language. It asks the questions your team would ask, understands the answers, and writes a structured record — who called, what they need, how urgent, what to quote. Anything it cannot handle is handed to a person with the conversation already summarised, so nobody starts from nothing.
What changes
Every call leaves a record, including the ones that used to vanish. The enquiry is in your CRM before anyone gets to the office, and a customer who speaks Spanish, Polish or Mandarin is not a customer you quietly lose.
Orders that get typed in twice
The pain — orders arrive as email, PDF or a web form, and somebody retypes them into the system. Slow, and every typo becomes a wrong delivery.
What we put in — the document is read automatically, fields are extracted and checked against your catalogue and prices, and only the genuinely unclear ones reach a human.
What changes — the keyboard work disappears, the errors it caused disappear with it, and orders stop queueing behind whoever does the typing.
Quotes that take days
The pain — pricing lives in one person's head and an old spreadsheet. Two salespeople quote the same job differently, and the customer has already called someone else.
What we put in — the pricing rules written down once, in software, and a quote assembled from your real cost data in minutes — with a margin check before it goes out.
What changes — quotes go out the same day, at prices you chose on purpose, and the business stops depending on one person being available.
Support answering the same question forever
The pain — most tickets are the same handful of questions. Real problems wait in the queue behind them.
What we put in — an assistant that answers from your own documentation and order history — not from the open internet — and routes anything it is not confident about to a person, with the context attached.
What changes — routine questions get answered immediately, and your team spends its day on the cases that actually need a human.
Approvals lost in inboxes
The pain — purchases, discounts and time off get approved in chat and email. Nobody can reconstruct who approved what, and an audit becomes a week of archaeology.
What we put in — approvals move into a workflow with rules, reminders and a permanent record. Small amounts clear themselves; the ones that matter reach the right person once.
What changes — nothing stalls because someone was on holiday, and the record exists before anyone asks for it.
Access nobody ever took away
The pain — staff join and leave, and their accounts stay open across a dozen systems. Customer data sits in a spreadsheet anyone can copy.
What we put in — one place where joining and leaving actually grants and removes access, sensitive data behind roles instead of goodwill, and a log of who saw what.
What changes — the obvious hole closes, and you can answer a security questionnaire from a customer without improvising.
Your operation, mapped
Every business is a set of moving parts that nobody has ever drawn on one page. The audit draws it — then we decide together which parts should stop being done by hand.
Book an audit →How the audit runs
-
Step 1
We watch the work
Interviews with the people doing the job, and we follow real cases end to end — not the process as written, the process as it happens.
-
Step 2
We put numbers on it
How often each step runs, how long it takes, where it stops, what it costs when it goes wrong. An opinion is not a finding.
-
Step 3
You get a ranked list
Every opportunity with its effort, its risk and what it frees up — including the ones we recommend you do not automate, and why.
Book an audit
Findings are yours to keep, with or without a build. Figures in the report come from your own operation — we measure, we do not estimate from the outside.
04 — Why us
Seven reasons clients
Seven reasons clients
stop shopping around.
-
1
One team, whole stack
App, backend, portal and AI layer built by the same people. No handoffs between vendors, no finger-pointing when something breaks between them.
-
2
Native-grade mobile
iOS and Android that feel like they belong on the device — not a web page in a shell that users delete after a week.
-
3
AI that earns its place
We integrate models where they cut a cost or a wait time, and we tell you when a feature does not need one.
-
4
Scope fixed in writing
Discovery ends with a written scope, a timeline and a number. What changes later changes by agreement, not by surprise invoice.
-
5
Business software that gets used
Internal tools and portals designed around the way your operations actually run, so the people inside the company stop working around the system.
-
6
We stay after launch
Store submission, monitoring and the iteration weeks when real users arrive — the part most studios hand back to you.
-
7
US-based, start to finish
Your time zone, your contracts, one accountable partner — not a chain of subcontractors you never meet.
05 — What we build
Four things, done properly.
Mobile apps
Consumer and internal apps for iOS and Android — onboarding, payments, offline behaviour, push, store submission and the release cadence after it.
Business software
The systems a company runs on: operations tools, back offices, dashboards, internal workflow software that replaces the spreadsheet nobody admits to.
Portals & integrations
Customer, partner and vendor portals wired into what you already run — CRM, ERP, billing, logistics — so data stops being re-typed between systems.
AI integration
Assistants over your own data, document and ticket automation, search that understands the question, forecasting on your numbers — connected to the product, not bolted beside it.
06 — Straight answers
The six questions
The six questions
everyone asks first.
Do you work fixed-price or time and materials?
Discovery comes first and ends with a written scope, a timeline and a number. A defined build then runs as fixed scope. Work on an existing system runs phased, because nobody can honestly fix the price of a codebase they have not opened yet — we scope one phase at a time and you decide at each boundary.
Who owns the code when it is done?
You do. Source code, the design system, the infrastructure definitions and the repository history are handed over. No licensing of our own framework back to you, no component you have to keep renting, no hostage situation if you later move to another team.
We already have a product and a team. Can you work with that?
Yes — that is the "Modernize existing" path. We start by reading what is there, map the gaps, and agree what we touch and what we deliberately leave alone. We work alongside an in-house team on shared conventions and review rules, or take a self-contained slice end to end. What we do not do is quietly rewrite everything because it is easier for us.
What happens after launch?
Store submission and rollout are part of the build, not an extra. After that come the unglamorous weeks when real users arrive and the product has to change — monitoring, crash triage, the fixes that only show up at volume. We stay for those, and we agree the shape of that period before launch, not after.
Do we actually need AI in this?
Often not, and we will say so. An AI layer earns its place when it removes a real cost or a real wait — triaging documents, answering from your own data, cutting a manual step that runs hundreds of times a week. If a feature works better as ordinary software, that is what we build. Shipping a model you do not need is the fastest way to a product nobody trusts.
What do you need from us to move fast?
One person who can decide, available for a short call each week. Access to the systems we have to integrate with, early rather than late. Turnaround on reviews measured in days. Nearly every timeline that slips, slips there — not in engineering.
Built with
- iOS
- Android
- Python
- Node.js
- .NET
- PHP
- LLM integration
- RAG
07 — Work with us
Built in the United States.
Built in the United States.
On purpose.
Your hours, your calendar
Working hours that overlap yours all day, not a two-hour window at the edge of someone else's night. Standups happen when you are awake.
One accountable partner
US contracts, US communication, and a single team that owns the result — not a chain of subcontractors you never meet and cannot call.
Built for your market
We build for the users, the app stores, the payment rails and the expectations of the market you are actually selling into.
08 — Start a project
Tell us what
Tell us what
you're building. We'll scope it.
Send the idea, the existing product, or the mess you want cleaned up. You get a scope conversation, not a sales call.
info@itrul.com