Engagement models
We agree the release, the owner and the acceptance criteria before adding team size or duration. Every engagement can start with ten days and stop there.
Start here
Most companies know they need AI and cannot say where. The first week tells you where it pays, ranked by value against difficulty. The second week builds the top one, so you finish holding working software rather than a recommendation.
If there is no working prototype at the end of day ten, there is no invoice.
Start a Deployment BriefEngagement models
Every engagement starts with the cheapest reversible commitment and expands only after a release is working.
Two weeks inside your business. Every department mapped, the opportunities ranked, and the top one already built against your real data. No working prototype, no invoice.
A senior team takes one workflow through to a production release your team is using. We will not quote a sprint before the brief. Ten days inside your systems turns an unknown into a fixed price you can approve.
Where you land in that range depends on:
You are buying a team rather than a scope: a dedicated pod working through a continuing backlog across several workflows, business units or locations.
Monitoring and maintenance for AI workflows and integrations already running in production.
What we need to begin
That is what the first week finds. What we do need is someone who can open doors across departments, and a business willing to act on what the map says.
Straight answers
A free audit buys a slide deck. $4,000 buys ten days of senior engineering time inside your systems and a working prototype on your real data. It is credited in full against a sprint, so if you continue it costs you nothing. And if there is no working prototype at the end of day ten, there is no invoice.
Because discovery has one price and implementation does not. Ten days with a fixed team costs the same whoever buys it, so we publish that number. Implementation effort varies with how many systems must be integrated, whether access and permissions already exist, whether a human approval path is required, and how many teams go live first. The brief turns those unknowns into a fixed number you can approve. A firm that quotes implementation before knowing them is either guessing or planning to re-quote later.
Yes. The quote comes out of the brief, after we have been inside your systems, and it is agreed with written acceptance criteria before the sprint starts. If we misjudged the effort, that is our problem, not a change request.
A stable cross-functional team working through a continuing deployment backlog, with a flat monthly fee and no per-hour billing. The minimum term is three months because a pod that rotates every few weeks stops being embedded. After the term it is cancellable, and everything built to that point is already in your repository.
No. Zylen is an implementation partner, not a software vendor. There is no Zylen platform you are required to license. You own the code and the IP from the first commit, and the handover is designed so your team can run and change the system without us.
Prices are published in USD. We invoice in INR for Indian customers and can quote in local currency elsewhere. Taxes are additional and depend on your jurisdiction.
Need scope before a commercial decision?
Ten days inside your systems establishes the workflow, the constraints, the owner and the acceptance criteria, and produces a working prototype before anyone commits to a sprint.