ARK

/ 09 · Be built arounddesign • engineering • data • in your office

Drawn · built · running

Custom software development, built around how your work flows

Software is personal. It runs your day.

We design and engineer the system your company is missing, around how the work really moves rather than how a tool assumes it does. Then our engineers sit in your office until it runs.

Software built around you09 / 09

Custom software

The system that doesn't exist yet, built around how the work actually flows.

What we doARK

In production
Intellreach, since September 2026
In build
A ten-department operations platform
Tested
2,480 automated tests on one system
Where we sit
In your office, until it runs

01 · The work in buildA ten-department operations platform for real-estate developers

  1. 01 · Drawn

    Ten departments. One database.

    A developer's whole operation, from the slab cast on site to the buyer's demand note, planned as one system around one database before the first screen was built.

  2. 02 · Counted

    Fifteen roles. Six doors from outside.

    Nine roles inside the developer's office, from the owner to the site engineer. Six portals for the people outside it: vendors, contractors, consultants, channel partners, buyers and tenants. Each sees only what is theirs, and the database itself enforces it.

  3. 03 · Built, and running

    One slab cast. Every department knows.

    Mark a slab complete on site and the platform raises the demand note of every booking tied to it, tells the sales team, and each buyer finds theirs in their own portal. Nobody types it twice, because there is only one record.

Construction, in the platform's build (demonstration data)01 ConstructionSlabs, drawings, sign-offs, daily reports1Slab completeSlab complete
02 SchedulingThe plan, the Gantt, meetings, SOPs
Purchase, in the platform's build (demonstration data)03 PurchaseRequisition to payment, signed and trackedVendors
04 ContractsWork orders, milestones, retentionContractorsConsultants
Budget, in the platform's build (demonstration data)05 BudgetBudget, committed and spent
Compliance, in the platform's build (demonstration data)06 ComplianceIOD, CC and OC, demand notes, expiries
Sales, in the platform's build (demonstration data)07 SalesInventory, bookings, demand notes, receiptsBuyersChannel partners3Demand notes raisedDemand notes4In the buyer's portalBuyer's portal
08 TenantsConsents, transit rent, receiptsTenants
09 LegalPapers, cases, hearings, land
The platform, in the platform's build (demonstration data)10 The platformInbox, documents, chat, one dashboard
One database2One recordOne record
departments in one platform
tables in one database
screens
roles: nine inside, six portals
tests passing: 120 unit, 57 in the browser

The platform's ten modules drawn as a plan: an illustration of how it is built. The screens are from the build, on demonstration data for a fictional developer. In build, not yet live.

02 · Why custom

Who this is for: the company whose work does not fit the tool

We do not sell a tool and a login. Custom software is for the company whose work has outgrown the tools it bought: when the pipeline, the roles and the reports do not fit the boxes, people keep the truth in spreadsheets beside the tool. We build the system that fits the work instead.

It is for the leader who can point to the spreadsheet everyone depends on and nobody owns. That spreadsheet is where the system starts.

The system that doesn't exist yet: what custom software means here

Here it means software written for how one company works, designed with the people who use it and carried all the way into production. A CRM for every role, from owner to assistant. An assistant whose reminders are kept by a clock with no AI in it. A platform, now in build, that runs ten departments of a real-estate developer.

Schedule of systems · 28 October 2026

Fourteen systems with our code in them since December 2025. Four in production.

  1. S-01IntellreachA CRM for enterprise sales: every enquiry in one record, the AI drafts, people decide, code computes every number.In productionsince September 2026
  2. S-02ARK AssistantAn executive assistant that turns what you say into timed tasks, and reminds you at the minute on a clock with no AI in it.In daily usesince August 2026
  3. S-03A WhatsApp ordering agentCustomers order by chatting. The AI reads the order; tested code sets every price, every total and every allergy alert.Livefor one restaurant
  4. S-04Two online stores, one engineTwo brands on one codebase: every payment verified on the server before an order counts as paid, shipping labels from the admin, every rupee kept in whole paise.Livethe first of the two
  5. S-05The real-estate platformTen departments of a developer's operations, six portals for the people outside, one database.In build
  6. S-06A voice-agent platformBilling, operations and a client portal around a self-hosted open-source voice engine.Built
  7. S-07ARK's content platformOur own platform for search and content: each client's Search Console, keyword plan and articles in one place.In useon our own work

Seven of them, as they stood on 28 October 2026. The others are internal tools, demonstrations and early builds.

Built around how the work actually flows: the gap analysis first

Before a line of code, we sit with the people who do the work and draw how it really moves: who hands what to whom, where it waits, where the same figure is typed twice. The gaps on that drawing, ranked by what they cost you, become the specification.

That is the gap analysis, and the system is built from it.

It is one of nine services that work as one system, from being seen to being built around.

03 · In production, and on the road

Intellreach: a deal with its AI briefing and the suggested next step

Intellreach: a CRM for every role, owner to assistant, and a fourteen-panel sales MIS

Intellreach is the CRM we built for enterprise sales, in production since September 2026. Every enquiry from every channel lands in one record, the AI briefs each deal and drafts each reply, and people decide. Code computes every number, and a fourteen-panel sales MIS, built and rehearsed, reads the quarter before it closes.

ways in, one pipeline
panels in the sales MIS
How Intellreach was built
The eActros cockpit's charging screen: target charge, energy flow and departure time

Lead designer: Ashish Kumar Mishra

Mercedes-Benz Trucks

The driver's digital cockpit: software designed around the person using it

Software is only as good as the moment someone uses it. For Daimler Truck, the second generation of the Mercedes-Benz Trucks digital cockpit was designed around the driver's hands, eyes and the road: one layout that holds in more than forty languages, and no task allowed more than twelve seconds of total glance time.

languages, one layout
seconds: the most glance time any task may take
The cockpit, in full

04 · Forward-deployed

Forward-deployed engineering: engineers in your office until it runs

Forward-deployed engineering means our engineers sit in your office until the system runs, learning how the work moves from the people who do it and changing the software the same week. The gap analysis maps the flow, the engineers live inside it, and the system is shaped by the floor, not by a requirements document.

Software is personal: it decides how your people spend their day. So the people who build it should know those people by name, and be in the room the first week it carries real work.

1Revised on the floorAn illustration.

How it is engineered: TypeScript, Postgres, tests, the AI behind a wall of code

In TypeScript on Postgres, with the tests in the repository and every number computed in code. The model handles language; deterministic code keeps every guarantee, from the price on an order to the minute of a reminder.

automated tests in ARK Assistant, run on every change
of them on the reminder path alone
database migrations in Intellreach
API routes in Intellreach

Counted in each system's code, October 2026

06 · Questions

Questions buyers ask

Why custom software instead of a SaaS tool?
Because the tool was built for the average company and yours is not average. When the pipeline, the roles and the reports do not fit the boxes, people start keeping the truth in spreadsheets beside the tool. Intellreach was built around how an enterprise sales team actually works: every role's own view, owner to assistant, and a fourteen-panel sales MIS that tells leadership what the quarter will close at.
What is forward-deployed engineering?
Engineers who sit in your office until the system runs, learning how the work moves from the people who do it and changing the software the same week. It is how we build what does not exist yet: the gap analysis maps the flow, the engineers live inside it, and the system is shaped by the floor, not by a requirements document.
How is it engineered?
In TypeScript on Postgres, with the tests in the repository and every number computed in code. ARK Assistant runs 2,480 automated tests on every change, 253 of them on the reminder path alone; Intellreach keeps the AI behind a wall of code so that it drafts and people decide.
Do you design the interface as well as build it?
Yes; the person using it comes first. The second generation of Mercedes-Benz Trucks' digital cockpit was designed around the driver's hands, eyes and the road: one layout that holds in more than forty languages, with no task allowed more than twelve seconds of total glance time.

Drawn. Built.

Tell us how the work moves. We'll build what's missing.

Next · The work · 8 case studies

Every service above is proved by a page in the work: the site, the search, the system, told the way it was built.

Keep scrolling
to the work that proves it