About FunJoin
Since 2020, FunJoin has operated as a technology services provider. Their core services include Mobile App Development. The company operates with a team of 10 - 49 professionals. FunJoin holds a 5.0-star rating across 2 client reviews. Overall, FunJoin is one of the options worth shortlisting for a technology project.
Where We Specialize
Industry Expertise
Typical Project Size
FunJoin Reviews
Write a ReviewA development partner who treated our roadmap as carefully as their own
Flynn Buchanan / GM of Technology - Pacific Rim Commerce GroupMay 07, 2026
Project summary: Serialisation requirements under new traceability legislation had a compliance deadline. Our supply chain system required targeted development to meet it — generalist knowledge was not sufficient.
I came into this engagement as a sceptic. We had been through a failed implementation with a previous vendor and I had high standards for what evidence of competence looked like before I would trust a partner with our core systems. This team earned that trust progressively — through the quality of the discovery documentation, the rigour of the technical proposals, the consistency of the sprint deliveries, and ultimately the stability of the production system. I no longer lead with scepticism when recommending them.
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
The engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk
Questions & Answers
CMS that preserved every byte of SEO equity from the old site while adding every feature we needed
Yuki Hashimoto / Head of Product Development - East Asia Commerce KKFeb 26, 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.
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 engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk
Questions & Answers
QA coverage that finally made Friday deployments feel like a professional activity
Omar Al-Farsi / Chief Technology Officer - Falcon Digital VenturesFeb 22, 2026
Project summary: Our internal product thinking was strong but our execution capability in this specific technology domain was limited. We needed depth, not generalism.
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.
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
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
DevOps toolchain that compressed our two-week release cycle to same-day deployments
Bilal Chaudhry / Co-Founder & CTO - Indus Software HouseFeb 18, 2026
Project summary: Our internal product thinking was strong but our execution capability in this specific technology domain was limited. We needed depth, not generalism.
What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
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
Multi-region setup that has delivered 99.97 percent uptime since go-live
Théo Beaumont / VP of Innovation - Laurentian Tech PartnersFeb 14, 2026
Project summary: Remote care had gone from an experiment to a core service line and our technology had not kept pace. We needed a robust, compliant telehealth platform in a timeline that the market would not wait for.
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.
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
The kind of web build that makes you wonder why you tolerated the old site for so long
Nora Al-Otaibi / VP of Engineering - Salam Digital SolutionsJan 04, 2026
Project summary: Our audience data was fragmented across eight tools with no single identity layer. Personalisation had become impossible without first solving the data foundation.
The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.
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 engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk