We read open applications
We have no open posting,we have an open door.
ALTAI Digital is run by two founders. The people who take the call, build the system and hand it over are the same people. There is no published role today, and we are not waiting for one to meet the right person.
The team is two people today.The third could be you.
There is no account manager and no approval tier in between. Because the person discussing the work is the person doing it, no days pass between a decision and the thing being built.
There is no published role right now.Applications are still read.
We do not keep a list of open positions on the site, because there is no role we are hiring for today. Writing a posting that does not exist would be as wrong as claiming a result we never measured.
Every application that arrives is read by both founders. When one lands close to the work we do, we write back without waiting for a posting to open.
No posting
There is no published role today. We do not write postings to make a list look full.
Applications open
What you send goes straight to the founders. No filtering system and no third party sits in between.
No timing promise
Because there is no open role, we do not promise a response time. When work fits, we write.
Three things are true today,and we do not write the rest.
A long list would have been easy to write. Instead we write the three things that actually hold today. Headings with nothing measurable behind them do not go on this page, for the same reason we do not claim a result we never measured in the systems we build.
Straight to the founders
No tier in between
With a team of two the whole job stays visible: the client conversation, the workflow that gets built and the number measured at the end all sit on the same table.
- You are where the decision is made
- You see the whole of the work
- Feedback arrives the same day
Location independent
We do not care where the work happens
We do not tie the work to an address. The only thing we look at is whether the build runs and whether what was promised got finished.
- Remote work
- Asynchronous writing
- Calls booked from the calendar
Current stack
The tools we build with
We do not resell a product; on every build we pick the tool the job needs. The stack we use is written out openly in the technology section of this site.
Next.js
Vercel
Supabase
PostgreSQL
n8n
Claude
We work across four areas.If your application touches one, we read it.
What follows is not a posting; these are the headings of the work we deliver to clients today. Each one has a live product page on this site, so you can read what we build from there.
01
Process automation builds
Working out the steps of a job, deciding which of them can be automated, then building the workflow and taking it live. Where human approval sits is designed at this stage too.
Read what we build02
AI agents and integration
Connecting models to the client's own data and systems, setting up the audit log, and making the output measurable.
Read what we build03
Web and interface development
Writing the interface people actually use on top of the workflows we build: boards, forms, and the pages that reach the client's own customers.
Read what we build04
Search visibility and content
Making sure a client is found when they are searched for, and checking the language and the accuracy of every sentence written.
Read what we buildWhat we look at,and what we do not.
We look at
- Finished work. A page that is live, a workflow that runs, a build that works.
- Moving on your own. In a team of two there is no tier handing out tasks.
- Clear writing. Every sentence that reaches a client is written by us.
- Willingness to measure. We measure before and after; what we cannot measure, we do not call a result.
We do not look at
- School name. Not where you studied, but what you finished.
- Years on paper. A CV that says ten years tells us less than one build that runs.
- Tool lists. Not which tool you know, but what you produced with it.
- CV formatting. Three well-written paragraphs are enough.
Three paragraphs are enough.There is no format requirement.
Send your application to a single address. Both founders read the email, and the founders write the reply.
Putting "Open application" in the subject line is enough.
- 01Write
Tell us what you do, what you finished, and what you would want to touch here. If something is live, add the link; that says the most.
- 02We read
The email goes straight to the founders. No filtering system and no third party sits in between.
- 03If it fits, we write
When an application lands close to our work we set up a call. Because there is no open role, we do not promise a timeline.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
