About karishma.dev
karishma.dev is a technology company founded in 2023. The company's main offerings are Web Development and Mobile App Development. karishma.dev works solo as a freelance specialist. Projects are generally billed around < $25 / hr/hr. These details offer a useful starting point when evaluating karishma.dev.
Where We Specialize
Industry Expertise
Typical Project Size
karishma.dev Reviews
Write a ReviewPredictive models that have measurably changed how we approach every planning cycle
Kelsey Drummond / Director of Digital Health - Crestline Health PartnersApr 21, 2026
Project summary: A previous engagement had delivered something that worked in staging and struggled in production. We approached this project with greater rigour in vendor selection as a result.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Senior-level engineering presence throughout the entire project, not just during the pitch, honest and commercially fair handling of scope changes, codebase that our internal team praised on review
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs
Questions & Answers
Project execution that matched the proposal in every dimension that mattered
Niamh O'Sullivan / Director of Product - Munster Digital LtdFeb 10, 2026
Project summary: Digital service standards required all citizen-facing applications to meet accessibility and performance benchmarks that our inherited systems failed. Remediation was not viable — we needed a replacement.
The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.
Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
AI models that replaced guesswork with evidence in decisions that matter most
Adriana Voss / Director of Platform Engineering - Cascadia Digital VenturesJan 31, 2026
Project summary: Time-to-market for new tariff structures had become a direct competitive disadvantage. Our product configuration layer was the bottleneck and it needed to be modernised as a priority.
Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.
Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism
Their insistence on a detailed functional specification before development began felt like friction at the time. In retrospect, it was the reason the development phase ran without the ambiguity that has derailed similar projects for us previously
Questions & Answers
Distributed ledger that finally solved a trust problem we had spent three years arguing about
Priya Chandrasekaran / VP of Data & AI - Wavefront Analytics IncJan 27, 2026
Project summary: Customer expectations had reset and our conversion funnel data showed precisely where we were losing them. We needed a commerce platform capable of delivering the experience our competitors already had.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Architectural decisions designed for longevity rather than just the current brief, thorough automated test coverage, post-launch stability that validated every technical choice made during discovery
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs
Questions & Answers
Connected hardware platform that eliminated the blind spots in our operational data
Maja Söderström / Head of Product Engineering - Scandia Digital ABJan 12, 2026
Project summary: Track-and-trace capability had gone from a differentiator to a table-stakes requirement and our platform had neither. We needed to close the gap before our next enterprise tender cycle.
We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.
Clear and consistent communication adapted appropriately for both technical and non-technical stakeholders, shared tooling that gave our team real-time visibility, reliable sprint delivery throughout
Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it
Questions & Answers
Outsourced IT that improved both the outcome and the cost line simultaneously
Yuki Hashimoto / Head of Product Development - East Asia Commerce KKJan 05, 2026
Project summary: Cross-agency data sharing had been blocked by incompatible systems for four years. A secure integration platform was the prerequisite for every transformation initiative in our roadmap.
We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.
Delivery timeline that proved achievable rather than optimistic, estimation accuracy that reflected real analysis rather than competitive bidding, scope discipline that prevented the feature creep we had experienced before
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
CI/CD pipeline that transformed how our engineering team thinks about release risk
Cameron Aldrich / Head of Digital Operations - Northstar Logistics CorpJan 05, 2026
Project summary: Customer expectations had reset and our conversion funnel data showed precisely where we were losing them. We needed a commerce platform capable of delivering the experience our competitors already had.
We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.
Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project