Questions owners ask before choosing a tech team.
Check the scope of responsibility, the first decision checkpoint, company control and the exit before choosing a provider. These answers describe Ego Eimi’s model and link to the detailed conditions.
01 / Read the commitments in context.
The short answers below do not replace the scope in your proposal. Read Foundation, Tech Team, guarantees and the evidence register.
02 / Common questions
Who is Ego Eimi for?
An established company with durable revenue, a material software dependency and nobody inside owning it. A current trigger, decision authority, account access and a roadmap beyond the immediate problem are part of the fit.
What is the first engagement?
Foundation is a fixed scope engagement over 4–8 weeks. The first two weeks are the review, followed by a decision checkpoint. Implementation establishes control and delivers the agreed first production change.
When is the Foundation deposit returned?
If the review cannot show at least 10× the two-week review fee in revenue, cost or risk removed that you agree is real, the deposit is returned and the engagement stops. If you agree the value but stop for budget, you keep the roadmap and there is no refund.
Do we control the accounts from day one?
Yes. Company control of code repositories, cloud, domains, data and credentials starts from day one. Rights to project-specific work transfer as milestones are paid. Embedded background IP has a perpetual, transferable license.
Can you work with software we buy?
Yes. Choosing, implementing, integrating and running bought software is part of the function. A large specialist implementation may need a separate implementer.
Who answers when a covered system fails?
The named operator and secondary specified in the agreement own the response within the coverage envelope. The contract defines the systems, severity, response window and escalation process.
Is ongoing coverage unlimited development?
No. The coverage schedule defines systems and the tier defines concurrent roadmap initiatives. Major builds are separate fixed projects. Round-the-clock response is included only when explicitly purchased.
What happens if we leave?
When Tech Team ends, the full offboarding package is due within 30 days: current code, system map, access inventory, runbooks, open issues, roadmap, vendor list, data export and transition sessions.
Updated September 14, 2026 · About the team
Your technology
Start with the business
Your business depends on it.
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.