Capabilities
Four core offers. Eight practices underneath.
Everything Conseiltek sells sits under one of four offers. Underneath them are the 8 practices that make each one real — identity, platform, data, security, and the work of keeping the result running once it is yours.
Core offers
What we are actually hired to do.
The four are not a menu of unrelated motions. They are one argument in four parts: find the software worth replacing, put engineers next to the problem, build with AI inside the architecture, and make it hold together with everything you already run.
SaaS Replacement
Identify the applications and manual workflows worth replacing, then build the replacement.
High recurring licence costs, overlapping products, spreadsheet-driven workflows, weak workflow fit, per-user pricing and vendor lock-in are the opportunities we look for. We establish parity on what you actually use, migrate the data, run in parallel, and cut over.
Practices under this offer
- SaaS replacement engineering — Replatform a licensed product onto infrastructure you own.
- Data and integration — Get your data out, and keep the seams working.
Forward Deployed Engineering
Engineers who work directly with your teams, at the intersection of software, AI, data, product and operations.
An FDE learns the actual workflow, works alongside your domain experts, turns ambiguous business problems into technical systems, and stays until the thing runs in production and someone can measure it. They are not developers for hire.
Practices under this offer
- Forward deployed engineering — An engineer inside your team, measured on your outcome.
AI-Native Application Development
Applications where AI is part of the architecture and the workflow rather than a bolt-on feature.
Agentic workflows, enterprise search and retrieval, document processing, extraction and classification, knowledge assistants, model integration and orchestration, and the human-in-the-loop design that makes any of it usable. With evaluation, observability, security and governance attached, because that is what separates a demo from a deployment.
Practices under this offer
- AI adoption and roll-out — Make AI land in the organisation, not just in the pilot.
Enterprise Integration and Modernization
The work that has to be true underneath everything else.
APIs and microservices, cloud-native development, legacy modernisation, data integration, identity and access, workflow orchestration, web and mobile applications, platform engineering, and production support with continuous enhancement.
Practices under this offer
- Cloud and platform engineering — AWS and Azure landing zones that pass an audit.
- Identity and user lifecycle — Joiner, mover, leaver — automated and provable.
- Security and compliance — Owned software still has to pass the auditor.
- Run — We operate what we built, on your infrastructure.
The practices
Each one has a page, and each page has a section telling you not to buy it.
Deliverables, the phases and their durations, the honest shape of the price, and the cases where the answer is to keep paying the vendor. Read the last one first.
SaaS replacement engineering
Replatform a licensed product onto infrastructure you own.
The core practice. We pick one expensive contract, establish real parity on the features you actually use, migrate the data, run in parallel, and cut over. Techtons shows exactly what that looks like before you sign anything.
Forward deployed engineering
An engineer inside your team, measured on your outcome.
Every engagement has one. The FDE is not an account manager with a laptop — they are a senior engineer who writes code in your repository, learns your domain, and stays until the thing works.
AI adoption and roll-out
Make AI land in the organisation, not just in the pilot.
Readiness assessment, tool selection and roll-out, process redesign around what the tools are actually good at, an internal enablement programme, and adoption measured in changed workflows rather than seat counts.
Cloud and platform engineering
AWS and Azure landing zones that pass an audit.
Multi-account or multi-subscription landing zones, network and identity baseline, CI/CD, IaC standards, secrets, observability and cost engineering. Every application in Techtons deploys onto this baseline.
Identity and user lifecycle
Joiner, mover, leaver — automated and provable.
Identity governance, birthright access, downstream provisioning, segregation of duties, and access certification campaigns your auditor can read. Warden, Gatepost, Tenure and Keyring in Techtons are the reference implementations.
Data and integration
Get your data out, and keep the seams working.
Extraction from the incumbent SaaS, schema mapping and reconciliation, an event backbone, and the integrations that made the old tool sticky — rebuilt natively so they are yours too.
Security and compliance
Owned software still has to pass the auditor.
Threat modelling, secure SDLC, SOC 2 and ISO 27001 control mapping onto the systems we build, evidence automation, and penetration test remediation. We tell you plainly where a vendor attestation is still the cheaper answer.
Run
We operate what we built, on your infrastructure.
SLOs, on-call, patching, upgrades, capacity and cost review. Priced per system, cancellable, and designed to hand back to your team the moment you want it. You own the code and the cloud account throughout.
Every one of them is evidenced in Techtons — 37 reference applications, Apache-2.0, with the architectures and the cost models attached.
How delivery runs
Discover. Prove. Deploy. Scale.
One delivery sequence, whichever offer you buy and whatever the commercial shape. Every stage ends in a document or a running system, and you can stop at the end of any of them.
01
Discover
Map workflows, systems, spend, pain points and opportunity.
Two weeks, fixed price, ending in a document you keep whether or not you continue: what the incumbent costs, what you use, where the manual work sits, and which opportunity is worth taking first.
02
Prove
Build a focused prototype or production slice that validates the technical and the economic assumptions.
One slice, deployed, against real data and real users. If the assumptions do not hold, this is where you find out, and it is the cheapest place in the whole sequence to find out.
03
Deploy
Integrate with enterprise systems, security, data and operations.
Identity, downstream systems, the data migration, the parallel run and the cutover. Production is the point at which the work counts, so it is planned from week one rather than appended.
04
Scale
Expand the capability, harden the platform, drive adoption, and identify the next replacement opportunity.
Adoption measured in changed workflows, the platform hardened against what production has taught us, and the next candidate chosen from evidence rather than from the renewal calendar.
How you contract
The practice is what we do. The commercial model is who holds the keyboard.
A separate axis from the delivery sequence above. None of the practices is sold as its own motion with its own team: you buy one of three commercial models, and the work happens inside it. The same engineers and the same code in all three.
Guide
You have a dev team. We hand them the blueprint.
Reference architecture, the code, the infrastructure-as-code, the migration plan and a weekly working session with the engineer who built it. Your team does the building. We make sure they are not discovering the hard parts in production.
Fixed monthly. 3-month minimum.
You have engineers and you want the blueprint, not the builders.
Join
Hire a Forward Deployed Engineer. They sit in your team.
One of our engineers joins your standup, your repo and your on-call rotation. They are measured on your outcome, not on hours booked. They write code in your codebase from week one and leave documentation behind them.
Monthly per engineer. 3-month minimum, 30-day exit.
You have engineers, but not the specific depth this needs.
Deliver
We take it end to end and hand over the keys.
Discovery, build, migration, cutover, production run, handover. We own the outcome and the date. At the end you get the repository, the infrastructure, the runbooks and a team trained to run it, or we keep running it for you.
Fixed price per phase. Run priced separately.
You want the outcome, not the project.
Where to start
Almost everyone starts with one contract.
Buy commodity, build advantage. Not a portfolio review and not a transformation programme: one line item, usually the most expensive or the one closest to renewal, taken through a two-week Discover that ends in a document you keep either way.
Week 1 — what you actually use
Usage telemetry, admin export, and interviews with the people who live in the tool. Most licensed products are used at about a third of their surface area, and the third that matters is rarely the third in the sales deck.
Week 2 — parity, architecture, cost
A parity matrix that names what we will not replicate, an AWS and an Azure architecture, an infrastructure cost model, and a delivery plan with dates and a team shape.
The answer may be no
Under about 150 seats, or where the vendor attestation is the product, or where the value sits in a network we cannot rebuild, we will write that down and you will not get a second call trying to talk you out of it.
Pick one contract. We will show you the replacement.
A two-week assessment: we take your single most expensive SaaS line item, establish what you actually use, and come back with a parity matrix, an architecture for AWS and Azure, a cost model and a delivery plan. Fixed price. If the answer is keep buying it, we will tell you that.