OpenLoop
Request an Audit

FAQ

Common questions about working with OpenLoop.

If your question is not here, write to us at hey@openloop.in.

Engagements & Process

What does a typical engagement look like?

Every engagement starts with a 60-minute discovery call. We map your current operations, identify the workflows worth automating, and produce a clear scope document. From that we give you a fixed price and timeline. If you agree, we build. The average engagement runs 4 to 12 weeks depending on scope.

How is the price set, and can it change?

We agree on a fixed price before we write a line of code. The price does not change unless you change the agreed scope. Scope creep is our risk to manage, not yours. If something in the brief turns out to be more complex than scoped, we absorb it.

What happens if we need changes after delivery?

Post-delivery changes are treated as a new, smaller scope. We quote them separately. There is no lock-in: you own the system and can engage any developer after handover. We offer ongoing support arrangements for clients who want them.

What is the minimum engagement size?

We typically work on engagements of two weeks or more. Very small one-page tools or scripts may not be the right fit; we are better suited to operational systems that replace a meaningful manual workflow. If you are unsure, the discovery call will tell you quickly.

Do you work outside India?

Our team is based in Srinagar and we work remotely with clients across India. We can engage international clients for suitable projects, though all contracts and billing are in Indian Rupees under Indian law.

Technical & Delivery

What technology do you build on?

Our standard stack is PHP, MySQL, and Linux for backend systems, with Tailwind-based interfaces where needed. For ISP-specific work we use FreeRADIUS, MikroTik RouterOS API, RADIUS AAA, and SNMP. We do not use trendy frameworks for their own sake; we use what is reliable and maintainable.

Who owns the code after delivery?

You do. All source code, database schema, and documentation are transferred to you as part of every delivery. We do not retain licences, subscriptions, or dependencies that would lock you to us.

Do we need to manage hosting?

We can deploy to your existing server, or recommend and set up a Linux VPS for you. We do not require you to use any managed hosting we control. Standard deployments run on Ubuntu or Debian with MySQL.

What documentation do we receive?

Every delivery includes a system overview document, user and admin guides, and deployment notes. If your team needs to maintain or extend the system themselves, we include architecture notes and inline code comments where appropriate.

Scope & Fit

What kinds of problems are you best at solving?

Operational bottlenecks with a clear cost: manual billing, manual provisioning, spreadsheet-based coordination, field team dispatch, subscriber management for ISPs. We work best where the problem is operational rather than purely strategic or brand-driven.

What are you not a good fit for?

Consumer-facing apps with millions of users, marketing or brand websites, SaaS products requiring ongoing product management, and open-ended retainers where the scope is undefined. We also do not take on projects where the ROI cannot be defined up front.

Can you maintain a system you did not build?

Yes, though we start with an audit of the existing codebase to assess quality and risk before committing to a fixed price for maintenance or extension work.

Still have questions?

The fastest way to get answers is a 60-minute call.

We will map your operations, tell you what's worth fixing, and give you a clear cost estimate. No obligation.

Get in Touch

What's your most expensive manual process?

Request a 60-minute ops audit. We'll map your operations, identify what's worth automating, and give you a clear cost and savings estimate — before you commit to anything.