How we work
From first call to
live deployment
No black boxes. No surprises on delivery day. Here's exactly how an iLogix engagement works — every step, every handoff, every checkpoint.
Free discovery call
Fixed scope before we start
Progress visible every week
Handover + training included
The engagement model
Six steps. No ambiguity.
Every project — whether it's a web platform, an AI automation, or a Fintralis deployment — runs through the same structured process. Scope, build, review, hand over.
1
Day 1
Discovery call — free, 30 minutes
We start by understanding what you actually need, not what sounds good on paper. You walk us through your challenge. We ask the awkward questions: what's broken right now? What does success look like in 90 days? What's been tried before? There's no sales pitch — just a direct conversation.
You get: A clear sense of whether we're the right fit — and if we're not, we'll say so.
2
Days 2–5
Scoping & proposal
After discovery, we do our own research — into your tech stack, your workflows, your pain points — and return with a written scope document. Not a vague pitch deck. An actual document: what we'll build, what's excluded, the timeline, the fixed cost, and every assumption we've made. You can push back on anything.
You get: A proposal you can actually evaluate — no hidden assumptions, no variable-cost surprises.
3
Week 1
Kickoff & environment setup
Once you sign off, we run a structured kickoff. You get access to our project workspace. We get access to whatever we need — credentials, APIs, data samples, internal contacts. The first milestone is a working dev environment or architecture diagram within the first week, depending on project type.
You get: A named contact who's actually building your project — not an account manager.
4
Ongoing
Build phase — weekly check-ins
We build in sprints with a shared progress tracker. Every week you see exactly what was done, what's next, and whether anything has changed. We don't disappear for weeks and resurface with a demo. If something unexpected comes up mid-build, you hear about it immediately — not on delivery day.
You get: Full visibility into build progress — the status of your project, at all times.
5
Final week
QA, review & sign-off
Before anything goes live, we run a structured QA pass — functional testing, edge cases, performance checks. You then review on staging. We address feedback. Only once you've signed off does anything go to production. The review round is built into the timeline and the cost — not an add-on.
You get: Nothing goes live without your explicit approval. No surprises after deployment.
6
Post-delivery
Handover, documentation & support
After go-live, we hand over everything: source code, documentation, credentials, and a walkthrough session for your team. A structured 30-day post-launch support window is included. Beyond that, ongoing retainer and support contracts are available — most of our clients stay with us well past the initial project.
You get: A clean, documented handover — you own it fully, and your team can actually use it.
How we think
What governs every decision
Not a values wall. These are the things that actually change how we scope, build, and communicate on every project.
Scope before we start
The proposal is a binding document, not a rough estimate. We define what's in, what's out, and what we're assuming — before any work begins.
No hidden variation
We use fixed pricing on clearly scoped work. If something genuine changes mid-project, we flag it immediately and agree on it in writing before proceeding.
Code you can inherit
We write code your next developer can read and maintain. Documentation, test coverage, clear architecture — not just a working demo that breaks when touched.
Problems surfaced early
If we hit a blocker or realise something won't work as scoped, you hear about it the same day — not on delivery day. Early information is fixable. Late surprises are expensive.
Pitchers are builders
The engineer who scopes your project is the person who builds it. We don't win the work with seniors and hand it off to juniors.
Measured in outcomes
We don't count hours billed or reports delivered as success. We measure whether your original problem is actually solved.
By service
Process by what you need
The same six-step model applies across every vertical — here's how each service area typically runs in practice.
Web & App Development
- Requirements + wireframe alignment
- Tech stack selection & architecture design
- Sprint-based build with weekly staging updates
- UAT on client test users or data
- Go-live + performance baseline
- Source code + documentation handover
AI & Automation
- Workflow audit — map current state
- Automation candidate shortlist & ROI estimate
- Pilot build on highest-impact workflow
- Test with real data, measure error rate
- Scale to remaining workflows
- Monitoring + fallback documentation
Fintralis Deployment
- AP data access & ledger mapping
- Free evaluation — identify duplicate exposure
- Full deployment + ERP integration
- First audit run + findings report
- Finance team walkthrough session
- Ongoing monitoring setup
Cybersecurity
- Security posture review & gap analysis
- Product & licence recommendation
- Procurement via verified partner channel
- Deployment & policy configuration
- Admin training for your team
- Ongoing monitoring & renewal management
Staffing & Talent
- Role brief & culture fit discussion
- Sourcing from vetted candidate pool
- Technical screening by domain expert
- Shortlist of 3–5 qualified candidates
- Interview coordination & offer support
- Post-placement 30-day check-in
Training & Upskilling
- Skill gap assessment & learning objective alignment
- Programme customisation to team context
- Batch scheduling & logistics confirmed
- Delivery: in-person or virtual
- Assessment & completion certificates
- GeM procurement if applicable
Common questions
Things people ask before they start
Direct answers. If you have a question that isn't here, ask it in the discovery call.
How long does a typical project take?
It depends on scope. A focused AI automation or integration typically runs 3–6 weeks. A full web platform is usually 8–16 weeks. Fintralis evaluation to deployment typically runs 2–4 weeks. We give you a milestone-level timeline in the proposal — not a range.
Is pricing fixed or time-and-materials?
We prefer fixed-price engagements on clearly scoped work. If requirements are genuinely exploratory — for example, an AI product with uncertain architecture — we can run an initial discovery sprint on a time-and-materials basis, then move to fixed price for the build.
What happens if the scope changes mid-project?
Genuine scope changes happen. We document them, agree on the additional cost and time in writing, and proceed only after you've approved. We don't do informal "while we're at it" additions that show up as surprises in the final invoice.
Who owns the code and IP?
You do. Full source code, assets, and IP transfer to you on delivery. We don't retain rights, lock you into proprietary tooling, or require ongoing licensing to use what we've built.
Can we work with you on an ongoing basis after the project?
Yes. Most of our clients move to a retainer or support contract after initial delivery. We offer structured retainer packages for ongoing development, maintenance, AI model updates, and security monitoring.
Do you work with international clients?
Yes. We serve clients across India, UAE and GCC, Southeast Asia, Australia, and Europe. International projects are managed through Upwork or direct contracts. All communication, documentation, and delivery are in English.
Can government departments procure from iLogix?
Yes. iLogix is a registered seller on the Government e-Marketplace (GeM). Central ministries, state departments, PSUs, and autonomous institutions can procure our IT services, staffing, training, and cybersecurity solutions directly through the portal.
Ready to start? Let's talk.
A 30-minute call costs nothing. You'll leave knowing exactly whether and how we can help.