Acuity IT Solutions Pvt. Ltd.

BACKGROUND

Please describe your company and position.

I am the Founder of Firefly Systems LLC

Describe what your company does in a single sentence.

IT services company focused on building scalable, high-performance digital products. We combine engineering excellence with innovation. From custom web and mobile applications to AI-powered solutions and offshore development teams, we deliver end-to-end technology services tailored to business needs

OPPORTUNITY / CHALLENGE

What specific goals or objectives did you hire Acuity IT Solutions Pvt. Ltd. to accomplish?

• A dedicated, end-to-end remote team
• Reduced management overhead
• Technical reliability
• A scalable, long-term partner

SOLUTION

How did you find Acuity IT Solutions Pvt. Ltd.?

Referral

Why did you select Acuity IT Solutions Pvt. Ltd. over others?

• Good value for cost
• Referred to me
• Company values aligned

How many teammates from Acuity IT Solutions Pvt. Ltd. were assigned to this project?

2-5 Employees

Describe the scope of work in detail. Please include a summary of key deliverables.

1. Core platform delivery — The Instatrux Mobile Application was designed and built end-to-end, alongside foundational Web Portal modules for the carrier and the broker covering driver settlements, fleet management, accounting, load creation and tracking, and load ID/numbering architecture — all core functionality has been completed and delivered.

 2. New feature and integration expansion — Ongoing work to extend platform capability, including a driver directory integration on the mobile app and a rate confirmation and carrier notification workflow on the web portal.

3. Security hardening — A major cross-cutting initiative to bring both the mobile app and web portal in line with OWASP security standards, covering authentication and authorization, API/controller-layer protections, and secrets and credential hygiene across frontend and backend components.

4. Performance optimization — Dedicated efforts to improve app responsiveness and backend efficiency across both products, targeting faster load times, optimized queries, and reduced resource overhead on mobile and web.

5. Code quality, refactoring, and technical debt reduction — Structured cleanup of legacy code, removal of technical debt, and improvements to coding standards across both the mobile and web codebases (frontend and backend).

6. System reliability and stability improvements — Targeted fixes to reduce fragility, improve fault tolerance, and strengthen the service and data layers on both platforms.

7. Accessibility compliance (WCAG 2.1 AA) — Work to ensure both the mobile app and web portal meet recognized accessibility standards, improving usability for all users.

 8. Quality assurance and test automation — Build-out of end-to-end and UI automation testing frameworks to improve release confidence and reduce regression risk across both products.

9. Delivery progress — Core build phases for both the mobile app and web portal are substantially complete (roughly 80%+ of tracked work items closed), with the program now focused on hardening, optimization, and quality rather than new ground-up development.

10. Overall program direction — With primary functionality live on both products, current priorities center on non-functional excellence (security, performance, reliability, accessibility) alongside a modest set of new feature integrations to round out platform capability. 

RESULTS & FEEDBACK

What were the measurable outcomes from the project that demonstrate progress or success?

1. Strong overall delivery progress — The majority of planned work across both the Mobile App and Web Portal has been completed, with the Web Portal slightly ahead in maturity compared to the Mobile App.
2. Core platform successfully delivered — The foundational mobile application was fully built and released, alongside major Web Portal capabilities including driver settlements, fleet management, and load numbering — establishing the core operational platform.
3. Consistent execution on planned work — A high proportion of engineering and operational tasks have been completed on schedule, reflecting steady team throughput and delivery discipline.
4. Meaningful feature progress with more in the pipeline — Roughly half of the planned features (user stories) have been delivered, with the remaining set actively in development as part of ongoing platform expansion.
5. Active defect management — A significant share of reported issues have been resolved, and high-priority defects are being tracked and remediated as part of a dedicated quality and hardening effort rather than left unaddressed.
6. Shift from build to maturity phase — The program has moved beyond initial development into a stabilization phase, with focused efforts now on security hardening, performance optimization, reliability, and accessibility compliance across both products.
7. Investment in long-term quality — New test automation frameworks have been introduced for both products, laying the groundwork for stronger regression coverage and release confidence going forward.
8. Balanced roadmap — Alongside stabilization work, new feature and integration efforts continue, showing the program is maintaining forward momentum rather than only doing cleanup work.

Describe their project management. Did they deliver items on time? How did they respond to your needs?

• Delivery discipline — The work has been organized into clearly scoped phases, moving from initial platform build-out to a structured stabilization phase covering security, performance, reliability, and accessibility. This phased structure suggests a deliberate, planned approach to delivery rather than ad-hoc execution, with major foundational components completed before hardening work began.
• Responsiveness to evolving needs — The backlog reflects an active shift in focus over time — from core feature development toward security hardening, performance tuning, and quality improvements — which indicates the team has been adjusting priorities as new requirements and risk areas were identified, rather than rigidly sticking to an original plan.
• Prioritization and risk management — Defects and issues are actively tracked and triaged by severity, with high-priority items called out and worked through a dedicated remediation effort rather than being left unaddressed. This points to a project management approach that surfaces and manages risk proactively.
• Scope and backlog management — Work is broken down into well-defined initiatives (epics) spanning both products, each with a clear theme (e.g., security, performance, accessibility, new features), suggesting organized planning and coordination across the mobile and web workstreams rather than siloed, disconnected efforts.
• Forward planning — The presence of newly initiated feature and integration work alongside ongoing hardening efforts suggests the team continues to plan ahead and take on new scope, rather than only reacting to issues — a sign of sustained engagement with the project's direction.

What was your primary form of communication with Acuity IT Solutions Pvt. Ltd.?

• Virtual Meeting
• Email or Messaging App

What did you find most impressive or unique about this company?

• Proactive quality culture beyond "just shipping features" — Rather than stopping once core functionality was delivered, the team voluntarily invested in security hardening, performance optimization, accessibility compliance, and technical debt cleanup across both products. This reflects a maturity-minded engineering culture that treats delivery as an ongoing responsibility, not a one-time handoff.
• Consistency across two distinct product lines — The same disciplined approach (structured phases, defect triage, hardening initiatives) was applied in parallel to both the mobile application and the web portal, despite them being different platforms with different technical demands. That kind of consistency suggests strong internal standards and coordination rather than one-off effort tied to a single team or product.
• Breadth of technical ownership — The scope of work touched nearly every dimension of software quality — security, performance, reliability, accessibility, and automated testing — rather than narrowly focusing on just new features or just bug fixes. That breadth is often a sign of a team that takes end-to-end ownership of the product rather than working strictly to a narrow spec.
• Willingness to prioritize non-glamorous work — Security hardening, accessibility compliance, and technical debt reduction are often deprioritized by vendors in favor of visible feature work. The fact that this was treated as a first-class initiative alongside new feature development is a notable differentiator.
• Balanced forward momentum — Even while addressing hardening and quality work, the team continued to take on new feature and integration scope, showing they didn't lose sight of business growth needs while cleaning up the platform.

Are there any areas for improvement or something Acuity IT Solutions Pvt. Ltd. could have done differently?

• Faster closure on high-priority issues — While defects and risk items are being tracked and worked through, there's room to tighten turnaround time on the most severe/high-priority issues specifically, rather than treating all open issues as a single undifferentiated backlog.
• More visibility into non-feature work — A meaningful portion of effort has gone into hardening, refactoring, and technical debt work that doesn't produce visible new functionality. Clearer, more proactive communication about this "behind the scenes" work — its purpose, progress, and business value — would help stakeholders better appreciate and track that investment. 
• Stronger testing coverage earlier in the lifecycle — Automated end-to-end and UI testing initiatives were introduced later in the project rather than from day one. Establishing that safety net earlier tends to reduce regression risk and rework as the platform scales.