Juric's software practice provides IT consultancy and delivers software to the businesses it advises. It is held to the same standard as the legal practice: a written scope, a named point of contact, and an expectation that what we deliver keeps serving long after the engagement is closed.
The shape of each engagement is set in conversation. For an initial enquiry a short note about the business and the problem is enough to begin; where the discussion turns to specifics we are glad to proceed under non-disclosure.
Advice on how a business should be served by its systems — what to build, what to buy, what to retire, and in what order. Engagements often begin as a review of what is already in place.
Software written for a specific business rather than adapted from something general. Web and mobile applications, internal tools, and the services behind them. We hand over source, documentation and deployment instructions as a matter of course, so that the work can be maintained by someone other than us.
Making existing systems work together — accounting, operations, and third-party services that were never designed to speak to one another. Includes data migration where a system is being replaced.
Ongoing care of software already in service — corrective fixes, dependency and security updates, monitoring, and incremental improvement under a retainer.
A short discussion of what the business does, what its systems currently do, and where the two have come apart. We are glad to work under non-disclosure from the outset.
30 minutesA note setting out what we propose to build or change, what is expressly out of scope, what it will cost, and what we need from you to start.
3–5 working daysWork proceeds in visible increments against the agreed scope, with a named point of contact. You see working software rather than status reports.
Project-dependentSource, documentation, credentials and deployment instructions are handed over on completion. A support retainer is offered but never assumed.
On completionThe software practice sits alongside the firm's legal and financial work rather than apart from it. The two meet in contracting, data handling and compliance. A software engagement frequently raises questions about what may be collected, what a vendor agreement should say, or what a regulator will expect, and on those the legal side of the firm is already in the room. Equally, a legal or accounting matter that calls for a system to be built does not need a separate vendor engaged. Each arm can also be engaged on its own.
Yes. Ownership of bespoke work passes to the client on payment, and that is set out in the engagement terms rather than left to be argued about later. Source code, documentation and deployment instructions are handed over as a matter of course.
Yes. A good deal of the work is alongside an in-house team or an incumbent supplier. Where we are asked to review work done by others we will say plainly what we find, and we do not treat a review as an opportunity to propose a rebuild.
No. Software and technology services are delivered on standard commercial terms and sit outside the scope of the Bar Council of India's rules, which apply to the legal practice. The disclaimer at the foot of every page sets this out.
Enquiry
All enquiries are received and responded to by email. We will read your note carefully and reply within two working days — usually sooner. Please do not send privileged or sensitive documents in the first message.