IT consulting
Tankar takes on advisory work where the question is a decision rather than a build. That includes a technology or architecture review, a build against buy comparison, due diligence on a system before an acquisition or an investment, a vendor or platform selection, and a delivery review of a project that is not going well. Every engagement ends in a written document with a recommendation, the reasoning and the evidence, and the document is useful whether or not Tankar does the work that follows.
A decision, not a deck
Advisory work here starts with the decision being made and the date it has to be made by. Everything in the engagement exists to make that decision better informed, and the output is a document rather than a presentation.
Evidence from your systems
Findings come from the repository, the incident history, the cloud bill and the people who operate the system. A reference architecture describes somebody else's company.
Useful without us
The report, the models and the raw findings are handed over so your team or another supplier can act on them. Advice you can only use by hiring the adviser is not advice.
Typical engagements
What this service usually produces, as deliverables rather than adjectives.
- Architecture and code review of an existing system, with findings ranked by cost and risk
- Build against buy comparison for a capability, with total cost of ownership over three years
- Technical due diligence before an acquisition or an investment round
- Platform or vendor selection with a scored comparison against your own criteria
- A delivery review of a project that is late, with the causes separated from the symptoms
- A technology roadmap for the next 12 to 18 months, sequenced by dependency and risk
How it runs
The stages this service goes through, and what you see at each one.
Framing
The decision being made, who makes it, what would change their mind, and the date it has to be made by. Written estimate within 48 hours of the scoped call.
The written estimate follows within 48 hours of the scoped call.
Evidence
Code, data, contracts, incident history and interviews with the people who operate the system, rather than a questionnaire sent to a manager.
Analysis
Options set out with their costs, risks and dependencies, including the option of doing nothing, which is often the one nobody costed.
Review
A working session on the draft with the decision-makers, so objections are answered in the document rather than after it.
Report
A written recommendation with the reasoning and the evidence, plus a sequenced plan if the recommendation is to act.
Handover
The document, the models behind it and a walkthrough. You can act on it with your own team or another supplier.
- Timeline
- Due diligence to a transaction deadline is scoped to that deadline.
- Team shape
- A senior engineer or architect who does the work, a project manager who runs the schedule, and specialists brought in for a specific area such as security, data or mobile.
Stack for this service
The technologies this work is usually built on, and why each one is used here.
| Technology | Why we use it here |
|---|---|
| Your existing systems | The evidence comes from the code, the incident history and the cloud bill you already have, not from a reference architecture. |
| Static analysis and dependency tooling | Gives a measurable picture of size, duplication, dependency age and known vulnerabilities instead of an impression from reading. |
| Cloud cost and usage reports | Total cost of ownership arguments need the real bill, broken down by service and environment. |
| Structured interviews | The people who operate a system know where it hurts. That evidence is not in the repository. |
| Written documents | A recommendation that cannot survive being written down and reviewed is not a recommendation. |
Selected work
Case studies where this service carried the engagement. Only outcomes with a source are shown.
Anonymised clientRetail and e-commerceA multi-vendor marketplace with vendor self-service and compliant invoicing
A marketplace where vendors onboard themselves, list and price their own stock, and are paid out against a commission engine with GST-compliant invoices.Services: E-commerce and marketplace development, Custom software development and 1 moreRead the case study
Anonymised clientLogisticsBooking and workforce scheduling for a home-services business
A booking and scheduling platform that assigns jobs to service partners by skill, area and availability without double-booking anyone.Services: Custom software development, Mobile app development and 1 moreRead the case study
Engagement models that fit
Advisory work is usually fixed price against a defined question and a delivery date.
Questions buyers ask
What buyers ask most about this service, answered before the first call.
Tell us what you are building.
NDA on request. Written estimate within 48 hours of a scoped call. Reply within one business day.