Techliphant pricing: every engagement quoted to its scope.
We do not publish ranges or starting figures. The right number depends on scale, deployment model, integrations, support level and contract length and inventing one without that context only creates anchors nobody trusts. Tell us the shape of the work; we will send a written, itemised proposal.
Itemised proposals
Platform, engineering, infrastructure, support and one-time costs broken out line by line, never bundled.
Pass-through at cost
Model providers, GPUs and cloud infrastructure billed at cost. Any management fee on top is disclosed up front.
No charge for scoping
Discovery calls, written proposals and revisions cost you nothing. We do not bill for our own sales process.
Three ways to engage us. Same senior people.
The shape of the engagement is the real cost driver, not an hourly rate. Pick the one that matches your stage and the kind of problem you are trying to solve every one of them is custom-quoted to your scope.
Discovery sprint
Audit, blueprint, roadmap and an ROI model. The best way to start when the problem is still being sized.
New problem space, exploring feasibility, or you need a plan to socialise internally before a larger commitment.
- Stakeholder interviews
- Technical audit
- Phased roadmap
- ROI model
- Risk register
Fixed-scope build
Well-scoped phases with clear acceptance criteria discovery has happened, the scope is real, the outcomes are measurable.
You know what needs to be built, the requirements are stable, and outcomes can be defined before kickoff.
- Architecture & UX
- Sprints with weekly demos
- CI/CD + tests
- Documentation
- Cutover plan
Embedded team
Dedicated senior engineers join your team on an ongoing basis sprint cadence, your tools, your standups.
Evolving roadmap, in-house product team, or you want continuous capacity without hiring full-time.
- Embedded engineers
- Weekly burn-down
- Real-time backlog
- On-demand architecture sessions
- Quarterly business reviews
Every engagement includes mutual NDA, signed DPA, encryption at rest and in transit, and audit logs.
Eight levers move every number.
Public ranges hide these. We surface them up front so you can see exactly what would move the proposal up or down and where you have room to trade scope for cost.
Scale
Users, data volume, transactions per second, regions.
Deployment model
Multi-tenant cloud, private cloud / VPC, or on-prem.
Integrations
Systems you need to connect and how clean their APIs are.
Geographic reach
Data residency, languages, regional compliance.
Support tier
Business hours, extended hours, or always-on coverage.
Contract length
One-off engagement vs. multi-year partnership.
One-time work
Migration, training, custom development, data cleanup.
AI usage
Token volume, retrieval load, model mix, evaluation depth.
From conversation to a real number.
Four steps from your first message to a proposal you can take to your CFO. No sales sequences, no follow-up theatre, no charges for any of it.
Tell us the shape
A short form or a 20-minute conversation. We learn what you have, what you need, who decides, and what is funded.
Discovery conversation
We go deeper on architecture, integrations, constraints and timing. No follow-up sales sequence one working session.
Itemised proposal
Every cost broken out line by line platform, engineering, infrastructure, support. Revisable until it fits.
Iterate together
Trim, expand, or phase the scope until the numbers and the timeline fit what you can fund. Then we start.
Want the full detail on a product? Each has its own page.
Every Tilarq product is custom-quoted the same way to your scale, deployment and integrations. Use the product pages to understand capabilities and shape; reach out when you are ready to scope.
Pricing questions, answered.
Because every engagement is custom-quoted. Scale (users, data, regions), deployment model (cloud, private, on-prem), integrations, support tier and contract length each move the number materially. Public ranges either mislead small buyers or scare large ones neither helps you.
Honestly, no a number invented without context becomes an anchor that nobody trusts later. Once we know the shape of the work (a short discovery conversation), we can talk numbers and trade-offs openly in the same session.
Fixed-scope suits well-defined phases discovery, prototype, MVP, single-product implementation where outcomes are measurable up front. Embedded teams suit evolving roadmaps, in-house product groups, or work where the scope is meant to flex.
Platform usage (Soliq tokens, retrieval load, model choice) is separated from engineering (fixed-scope or embedded). Model providers, GPUs and cloud are pass-through at cost; the management fee on top is disclosed line by line.
No. Every proposal breaks out platform, engineering, infrastructure, support and any one-time costs (training, migration). Pass-through items are itemised. We do not bill for sales calls, discovery, or proposal revisions.
Yes. Most engagements open with a discovery sprint or a focused prototype before any larger commitment. If we do not think the problem is worth solving, we will tell you that too.
You own the code, the data, the runbooks and the documentation. We will help you transition to in-house ownership, or stay on for managed operations your call, written into the contract.
Ready when you are
Let's build something exceptional.
Tell us about your business, your stack, and the problem you are trying to solve. We respond with a clear next step usually a 30-minute discovery call, no fluff.
