How We Build Products at Apollo

Surgical Execution

People always ask how we run a publicly listed NBFC with just 30 people. Well, the answer lies in how we build at Apollo. It’s not just about using technology or building automated products, but about building efficiently. We focus on delivering the most bang for your buck, building with surgical-level precision, and avoiding the biggest pitfalls plaguing tech companies today, like over-engineering and creating features without long-term users. Here’s a look at our playbook for achieving this:

1. Sourcing Requirements

Our journey begins with a spark of inspiration, either from our ingenious internal teams or from our beloved external lending partners. When a requirement flows in, we dive into the task manually first. This step is our secret sauce, offering a plethora of benefits:

• Grasping the Problem: It helps us really understand the heart of the issue.

• Uncovering Surprises: We spot potential edge cases that might otherwise slip through the cracks.

• Future-Proofing: It lets us see if the feature is a long-term necessity or just a temporary fix.

And when it comes to requests from our lending partners? We prioritise those based on their current scale with us and their potential to grow even bigger!

2. Drafting the Requirement Document

After we've rolled up our sleeves and gotten hands-on, a point of contact (POC) drafts an initial requirement document. This masterpiece includes:

• Operational Insights: Detailed from an operational perspective.

• Thorough Details: Packed with all the nitty-gritty details to cover every angle.

3. Finalizing the PRD

Next, the Product Manager (PM) teams up with the POC to refine this document into a final Product Requirement Document (PRD). The PRD is our playbook, divided into three sections:

• Goal: A concise description of the feature's main objective.

• Impact: Quantitative KPIs to measure the feature's success.

• Detailed Description: Requirements laid out in simple, jargon-free language so everyone can get on board.

Once our PRD is polished to perfection, it’s shared with the relevant department for signoff.

4. Prioritizing Tasks

With a signed-off PRD in hand, we prioritize tasks based on:

• Effort and Man-Hours: Calculating the resources needed.

• Business Impact: Evaluating how the feature will boost key business KPIs.

5. Breaking Down Tasks

We then break down each task into smaller, bite-sized pieces akin to minimal viable products (MVPs). This strategy ensures:

• Frequent Releases: Regular updates keep the momentum going.

• Early Feedback: Continuous user feedback helps us fine-tune as we go.

6. Monitoring Progress

We keep a close eye on our progress. If all systems are go, we discuss the next phase with the team’s POC. This ensures:

• Awareness of What’s Next: The POC is always in the loop.

• Alignment: Both teams stay synchronized like a well-oiled machine.

7. Testing and Deployment

Our thorough PRD is a lifesaver when it comes to testing. The same document guides both the tech team and the department POC, ensuring top-notch technical and subject matter expertise. After testing, we deploy the feature and use analytics to measure its impact, guided by the KPIs set in the PRD.

8. Monthly Tech Updates

Every month, the tech and product teams put on a show with a tech update presentation, covering:

• Last Month’s Hits: Quantitative impact analysis of recent features.

• New Releases: The latest and greatest features fresh out of the oven.

This process keeps everyone accountable and fosters a data-driven approach to development.

9. Quarterly Housekeeping

Quarterly, we do some housekeeping on Sonic to identify:

• High-Utilization Features: Doubling down and making these beloved features even better.

• Underutilized Features: Analyzing and understanding the lack of use, reviving if possible, or learning from these to avoid future redundancies. If truly redundant, we eliminate them from our codebase to keep it lean and mean, reduce bugs, and lower AWS costs.

Conclusion

Our meticulous approach to product development at Apollo ensures that every feature we build is not only necessary and impactful but also a joy to create and use. By maintaining a structured yet flexible process, we continuously improve our products, driven by data and enriched by user feedback.