Inside your company, experienced engineers advance your development.
Experienced engineers who use AI across every step of development join your team and work alongside you.
You choose how to build.
When it's time to build, there's more than one way. You can hand the whole thing over as a set and have it delivered, or have engineers join your team and build with you inside. You choose, based on your situation. This page is about the latter: building together, in-house.
- hard to send outside
- expert eyes, close by
- keep the capability in-house
When development is hard to send outside for reasons like security, when you want expert eyes close by, or when you want to keep the capability in-house, building together inside fits well. If you'd rather hand it all over and have it delivered, see Custom Development.
With the same AI, software-development knowledge changes what comes out.
It's not just being able to use AI. Using it on a foundation of software-development expertise makes the results visibly different.
The AI is the same on both. What differs is the underlying knowledge.
What matters isn't "can use AI" but being able to evaluate the design and code AI produces and decide whether to keep it or throw it out. Modern development in the cloud (Azure/AWS, IaC, Scrum) is our home ground. Porting legacy mainframes/hosts and large fixed-scope SI are out of range.
Which step, and how AI is used there. That's what stays in-house.
As we work alongside you on-site, "which task, and how AI is used on it," from design to estimates, builds up as know-how inside your company. The more sprints run, the more it accumulates in-house, sprint by sprint.
runs inside your company — this way of working stays in-house
■ = this way of working remains with your team
We use AI as a matter of course across every step of development. So unlike working with engineers who don't use AI, the skill of wielding AI itself moves into your team. This is Tech Reis's own daily practice: we run our own product "Strix" this way every day.
This is Tech Reis's own record of how we actually work (Strix development).
You choose the contract form. And you can change it later.
Whether engineers join and build with you inside, or you hand the whole thing over as a set—you can start from either one. Changing the form partway is one of the options too.
On-site ⇄ full set. Start from either one, and you can change partway.
Which form fits depends on your situation and what you want to build. There's no need to lock it in. Cost is quoted individually by setup, period, and contract form (we don't post figures). We also take on general development support that isn't limited to AI.
First, let's read your current moment together.
How many people, for how long, in which contract form—none of it needs to be decided. In a 60-minute free consultation we sort it out together, including whether an on-site team even fits.
Consultation takeaway sheet
- a read on the setup you need (how many, how long)
- a proposed approach (on-site / switch / traditional—which fits)
- a rough read on scale (sense of size, not a figure)
From one person. Start small, with a few-weeks "trial."
Honest questions we often get
What contract form is it? Can it change partway?
There are two forms. ① Joining your team for just what you need (quasi-mandate, on-site)—for when you want to decide as you build and keep the capability in-house. ② Taking on the whole thing as a set (contracted build)—for when what to build is fixed and delivery ends it. You can start small with ①, and once it's proven you can talk about switching to ②. Either way, it's fine to come in undecided.
How much does it cost?
Because it depends on the setup you need (how many people, how long, which contract form), we don't put out a single figure. We hear your situation and give a rough read on the spot. Start with a free consultation. You can begin from one person and a few-weeks trial, so it never has to start as a big contract. Monthly work can be set with an agreed upper and lower bound, and how to handle going over or under is decided together at contract time.
With an on-site team, how do direction and progress tracking work?
They work as a member of your team, joining your sprint (your weekly rhythm). Progress stays visible day to day because the work layout and the checks on changed code remain as records. The give-and-take of work can be arranged through a lead on our side—we set up the on-site collaboration to fit your setup.
If we pay by time, isn't the outcome hard to see?
We build small and show you working software on short cycles. Every few weeks you can see "what's done now," so it's a way of working where you pay by time but confirm the result every time. It won't be money vanishing while someone sits and waits.
AI writes it—do they actually understand what's inside?
AI is used for drafting and completion; the decision of whether to keep it stays with the person (the engineer). Design intent, review decisions, test edges, whether to merge—a person always judges the key points. Because they have software-development knowledge (expertise), they can evaluate the design and code AI produces and throw out the mistakes. That's the difference from someone who can "just use AI."
Outside people will touch our source and customer data…
Confidentiality, access narrowed to only what's needed, and discipline around taking things out—we set these up as a matter of course. Rather than demanding a thick, rigid agreement from the start, we begin by fitting to your rules.
Can we step out if it's not a fit? Won't it get locked to one person afterward?
Only for as long as you need. Scaling up, scaling down, and ending are all open to discussion (unlike full-time hiring, it doesn't become a fixed cost). The environment stays in a form you can rebuild from the same settings any number of times, so handover isn't a problem. And while AI use is at the core, we also take on general development support that isn't limited to AI.
As an engineer, I'd like to work on this team?
Welcome. For the way of working—wielding AI in the field—and details on openings and hiring, see the careers section at the bottom of the page. You can also estimate your income there.
First, just talk with us about what setup fits.
In a 60-minute free consultation, we read the approach and setup that fit your company together.
From here on, this is for people who work here.
For engineers who wield AI in the field.
Wielding AI on a foundation of skills built in the field. That way of working, here at Tech Reis.