About Codal

It is a UX design & development company. Their clients have ranged from small business to business, but our philosophy has always remained the same: to empower brand visibility & deliver the most classic web & mobile solutions possible. Their goal is to train designers & developers alike, as well as keep clients aware of modern and upcoming trends.

Last updated May 13, 2026

Services

Mobile App Development Wearable App Development UI-UX Design

Industries Served

Gaming & Gambling Sports & Fitness Energy & Utilities Nonprofit & NGO Insurance Advertising & Marketing

Codal Reviews

Write a Review

Headless CMS that finally allowed our designers and developers to work in parallel

Sebastian Lapointe / CTO - Boreal Systems Inc
Verified
May 29, 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.

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.

PROS

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

CONS

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

4.5
Overall
4.5
Quality
4.5
Schedule
5.0
Cost
4.0
Communication
Project TypeCMS Development
IndustryGaming & Gambling
Project Cost$10,000 to $49,999
DurationAug 2025 – Mar 2026

Questions & Answers

Please describe your company, your role, and the industry you operate in.
Boreal Systems Inc is an established Gaming & Gambling organisation headquartered in Toronto, Canada. My role as CTO covers both strategic planning and operational technology delivery. We maintain high standards for our vendors because our clients hold us to high standards — a bar we expect our partners to meet.
What specific problem or business challenge led you to hire this company?
Our platform had been maintained by a previous vendor for three years and the accumulated technical debt had reached a point where delivery velocity had dropped to a fraction of what it should have been. We needed fresh engineering expertise and a structured plan to address the underlying issues.
What services did the company provide for your project?
End-to-end CMS Development delivery with particular depth in the integration and data migration components, which were the highest-risk elements of the programme. They supplemented this with a dedicated QA resource throughout development and a documented runbook for our operations team at handover.
Why did you choose this company over other providers you considered?
We ran a structured shortlisting process across five vendors. The technical evaluation eliminated two immediately. Of the remaining three, this team's proposal was differentiated by the specificity of their CMS Development approach and the evidence base they provided — reference projects in Gaming & Gambling contexts, not generic case studies. The reference calls confirmed a track record that the proposal had described accurately.
How clearly did the company understand your requirements and business goals?
Comprehensively. The discovery phase they ran was more thorough than anything we had experienced with previous vendors. They challenged requirements that were vague or contradictory, proposed alternatives where our initial thinking was limiting, and produced a functional specification that our internal stakeholders agreed was the clearest articulation of the product they had seen written down.
How was your overall experience with their communication and project management?
Communication was proactive, timely, and appropriately calibrated. Technical updates for the engineering audience, executive summaries for the steering group, risk flags with proposed mitigations rather than just problem statements. The fortnightly sprint reviews gave our stakeholders visibility without requiring them to attend every working session.
Did the company deliver the project on time and within your expected budget?
Yes. I had privately built a contingency expectation into my planning given the project complexity and the number of integrations involved. None of that contingency was needed. The delivery landed on the agreed date and the final invoice matched the approved budget to within a fraction of a percent. That outcome is rarer than the industry acknowledges.
What tangible results or business impact have you seen since the project was completed?
Quantifying the impact precisely is complicated by other variables in our business, but the metrics we can attribute directly to the CMS Development work are meaningful: session duration up, conversion rate up, error rate down, and our NPS for the digital touchpoint has improved by eleven points. Our account managers report that the new capability is coming up positively in client conversations.
What did you like most about working with this company?
The post-launch behaviour. Some vendors consider go-live to be the end of their professional obligation. This team treated it as the transition to a different kind of engagement. The hypercare period was substantive, the documentation was thorough and genuinely useful, and they checked in proactively at the thirty-day and ninety-day marks to review production metrics with us.
Would you recommend this company to others, and would you work with them again?
Unreservedly. We are in active scoping conversations for a second engagement and I expect this to develop into a multi-year partnership. For any organisation in the Gaming & Gambling sector looking for CMS Development expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

Commerce platform that handled peak-day traffic at twelve times normal load without incident

Radosław Kowalczyk / Head of Development - Wisła Software Sp zoo
Verified
Apr 14, 2026

Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.

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.

PROS

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

CONS

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

5.0
Overall
5.0
Quality
5.0
Schedule
5.0
Cost
4.5
Communication
Project TypeE-commerce Development
IndustrySports & Fitness
Project Cost$10,000 to $49,999
DurationNov 2025 – Mar 2026

Questions & Answers

Please describe your company, your role, and the industry you operate in.
I lead technology at Wisła Software Sp zoo, a growth-stage Sports & Fitness business based in Warsaw, Poland. As Head of Development my remit spans product engineering, platform operations, and strategic vendor partnerships. We had reached an inflection point where our internal capacity was not sufficient to execute our roadmap at the pace our market required.
What specific problem or business challenge led you to hire this company?
Regulatory requirements in our Sports & Fitness segment had changed and the compliance timeline was set by our regulator, not by us. The E-commerce Development changes required were significant enough to justify engaging a specialist partner rather than diverting our internal team from the product roadmap.
What services did the company provide for your project?
The core engagement was E-commerce Development delivery, though their scope expanded to include technical consultancy during discovery that materially improved our requirements. They also took ownership of the third-party integration workstream that had been a coordination challenge in previous projects, removing that complexity from our internal team entirely.
Why did you choose this company over other providers you considered?
The quality of the questions they asked during the briefing process was the first indicator. Vendors who ask precise questions in the sales phase tend to apply the same rigour during delivery. That hypothesis proved accurate. The technical proposal was substantive, the team structure was senior throughout, and the pricing was transparent.
How clearly did the company understand your requirements and business goals?
Thoroughly and precisely. The requirements document they produced was detailed enough that our QA team used it directly to write acceptance criteria. Every user story had a defined business objective attached. Nothing was left to interpretation. That discipline in the requirements phase paid dividends throughout development and testing.
How was your overall experience with their communication and project management?
The project management framework was the most structured I have experienced with an external vendor. Sprint planning was tight, acceptance criteria were specific, retrospectives were honest and acted on. The project manager treated the shared backlog as a live document and the risk register as an operational tool rather than a compliance artefact. I never had to ask for a status update.
Did the company deliver the project on time and within your expected budget?
Yes to both. There was a single sprint where a dependency on a third-party API introduced a one-week delay. The team identified it three weeks in advance, presented two mitigation options, and we agreed on an approach that recovered the schedule within the same sprint cycle. That level of foresight is what separates good project management from reactive problem management.
What tangible results or business impact have you seen since the project was completed?
The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.
What did you like most about working with this company?
The post-launch behaviour. Some vendors consider go-live to be the end of their professional obligation. This team treated it as the transition to a different kind of engagement. The hypercare period was substantive, the documentation was thorough and genuinely useful, and they checked in proactively at the thirty-day and ninety-day marks to review production metrics with us.
Would you recommend this company to others, and would you work with them again?
Absolutely. With a specific note that the value starts in the discovery phase — clients who approach that process with seriousness will get the most from the engagement. We invested appropriately at the front end and the returns are evident in what was delivered.

User research that uncovered friction we had stopped noticing because it was always there

Erik Lindqvist / Chief Technology Officer - Nordic Cloud AB
Verified
Apr 02, 2026

Project summary: Grid modernisation funding required us to demonstrate demand-response capability. The machine learning models existed on paper; we needed an engineering partner to build and productionise them.

Six months after go-live our platform is processing three times the transaction volume we specified in the original brief. The architecture choices made during discovery accommodated that growth without remediation work. That is the difference between a team that designs for what you tell them and a team that designs for what you are likely to need. We are in conversation about a Phase 2 engagement and I expect to be using this partnership for several years.

PROS

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

CONS

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

4.5
Overall
4.5
Quality
4.5
Schedule
4.0
Cost
4.5
Communication
Project TypeUI/UX Design
IndustryEnergy & Utilities
Project Cost$500,000+
DurationAug 2025 – Feb 2026

Questions & Answers

Please describe your company, your role, and the industry you operate in.
Nordic Cloud AB operates in the Energy & Utilities sector with headquarters in Stockholm, Sweden. In my role as Chief Technology Officer I am accountable for the full technology agenda — infrastructure, product, and vendor relationships. We are a commercially driven organisation and every technology decision is evaluated against a clear business case before it is approved.
What specific problem or business challenge led you to hire this company?
The immediate problem was that our UI/UX Design capability had become the bottleneck limiting our ability to grow. Every feature request, every new client requirement, every internal initiative was delayed by a platform that had been extended beyond its original design. We needed a rebuild, not a patch.
What services did the company provide for your project?
The core engagement was UI/UX Design delivery, though their scope expanded to include technical consultancy during discovery that materially improved our requirements. They also took ownership of the third-party integration workstream that had been a coordination challenge in previous projects, removing that complexity from our internal team entirely.
Why did you choose this company over other providers you considered?
We ran a structured shortlisting process across five vendors. The technical evaluation eliminated two immediately. Of the remaining three, this team's proposal was differentiated by the specificity of their UI/UX Design approach and the evidence base they provided — reference projects in Energy & Utilities contexts, not generic case studies. The reference calls confirmed a track record that the proposal had described accurately.
How clearly did the company understand your requirements and business goals?
Thoroughly and precisely. The requirements document they produced was detailed enough that our QA team used it directly to write acceptance criteria. Every user story had a defined business objective attached. Nothing was left to interpretation. That discipline in the requirements phase paid dividends throughout development and testing.
How was your overall experience with their communication and project management?
Outstanding. The discipline around asynchronous communication was particularly effective given the time zones involved between Stockholm, Sweden and the delivery team. Written updates were specific and consistent, response times were same-day for anything that required a decision, and nothing fell through the cracks across a six-month engagement.
Did the company deliver the project on time and within your expected budget?
Yes. I had privately built a contingency expectation into my planning given the project complexity and the number of integrations involved. None of that contingency was needed. The delivery landed on the agreed date and the final invoice matched the approved budget to within a fraction of a percent. That outcome is rarer than the industry acknowledges.
What tangible results or business impact have you seen since the project was completed?
The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.
What did you like most about working with this company?
Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.
Would you recommend this company to others, and would you work with them again?
Yes, without reservation. I have already made two direct referrals within my Energy & Utilities network — in both cases to peers facing UI/UX Design challenges similar to ours. I gave those referrals with confidence because I knew the experience I described was reproducible, not the result of exceptional circumstances on our engagement.

A technology investment that delivered returns ahead of the business case we approved

Jia Hui Tan / VP of Engineering - RedDot Technologies Pte Ltd
Verified
Feb 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.

Six months after go-live our platform is processing three times the transaction volume we specified in the original brief. The architecture choices made during discovery accommodated that growth without remediation work. That is the difference between a team that designs for what you tell them and a team that designs for what you are likely to need. We are in conversation about a Phase 2 engagement and I expect to be using this partnership for several years.

PROS

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

CONS

Pipeline availability for kickoff required a few weeks of lead time — in hindsight that selection pressure means you are working with a team that is in demand for the right reasons

4.5
Overall
5.0
Quality
5.0
Schedule
5.0
Cost
5.0
Communication
Project TypeIndustry-Specific Solutions
IndustryNonprofit & NGO
Project Cost$10,000 to $49,999
DurationJun 2025 – Jan 2026

Questions & Answers

Please describe your company, your role, and the industry you operate in.
As VP of Engineering at RedDot Technologies Pte Ltd I oversee technology investment and delivery across our Nonprofit & NGO operations in Singapore. We are a commercially focused business and our technology choices are always evaluated in terms of their direct contribution to business outcomes rather than technical elegance alone.
What specific problem or business challenge led you to hire this company?
We had a defined product vision for our next phase of growth in the Nonprofit & NGO market but lacked the engineering depth internally to execute it. The Industry-Specific Solutions requirements in particular required specialist experience that we could not realistically recruit for on the timeline our business plan required.
What services did the company provide for your project?
End-to-end Industry-Specific Solutions delivery with particular depth in the integration and data migration components, which were the highest-risk elements of the programme. They supplemented this with a dedicated QA resource throughout development and a documented runbook for our operations team at handover.
Why did you choose this company over other providers you considered?
A trusted peer in the Nonprofit & NGO sector had used them for a comparable Industry-Specific Solutions engagement and their recommendation was unequivocal. Our own due diligence confirmed the pattern they described. The combination of domain knowledge, Industry-Specific Solutions depth, and demonstrated delivery discipline was the deciding factor.
How clearly did the company understand your requirements and business goals?
Comprehensively. The discovery phase they ran was more thorough than anything we had experienced with previous vendors. They challenged requirements that were vague or contradictory, proposed alternatives where our initial thinking was limiting, and produced a functional specification that our internal stakeholders agreed was the clearest articulation of the product they had seen written down.
How was your overall experience with their communication and project management?
Communication was proactive, timely, and appropriately calibrated. Technical updates for the engineering audience, executive summaries for the steering group, risk flags with proposed mitigations rather than just problem statements. The fortnightly sprint reviews gave our stakeholders visibility without requiring them to attend every working session.
Did the company deliver the project on time and within your expected budget?
Yes. I had privately built a contingency expectation into my planning given the project complexity and the number of integrations involved. None of that contingency was needed. The delivery landed on the agreed date and the final invoice matched the approved budget to within a fraction of a percent. That outcome is rarer than the industry acknowledges.
What tangible results or business impact have you seen since the project was completed?
The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.
What did you like most about working with this company?
Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.
Would you recommend this company to others, and would you work with them again?
Yes. I would add the context that this is not the cheapest option in the market and they are selective about the engagements they take on. If your primary criterion is price, there are alternatives. If you want a technology partner who can be trusted with a complex Industry-Specific Solutions programme in the Nonprofit & NGO space and will deliver against a serious brief, this is the team.

Accessibility-first approach that broadened our audience and impressed our enterprise clients

Gustavo Ferreira / VP of Technology - Amazônia Digital Ltda
Verified
Feb 06, 2026

Project summary: Our actuarial models had outgrown the reporting infrastructure feeding them. Data latency was introducing risk into pricing decisions that the business had decided it could no longer accept.

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.

PROS

Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring

CONS

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

4.5
Overall
4.5
Quality
4.5
Schedule
5.0
Cost
5.0
Communication
Project TypeUI/UX Design
IndustryInsurance
Project Cost$500,000+
DurationJun 2025 – Nov 2025

Questions & Answers

Please describe your company, your role, and the industry you operate in.
Amazônia Digital Ltda operates in the Insurance sector with headquarters in São Paulo, Brazil. In my role as VP of Technology I am accountable for the full technology agenda — infrastructure, product, and vendor relationships. We are a commercially driven organisation and every technology decision is evaluated against a clear business case before it is approved.
What specific problem or business challenge led you to hire this company?
Our platform had been maintained by a previous vendor for three years and the accumulated technical debt had reached a point where delivery velocity had dropped to a fraction of what it should have been. We needed fresh engineering expertise and a structured plan to address the underlying issues.
What services did the company provide for your project?
The scope covered the full UI/UX Design lifecycle: discovery and requirements definition, solution architecture, iterative development across twelve sprints, integration testing, performance validation, production deployment, and a structured four-week hypercare period. They also provided system documentation and a knowledge transfer programme for our internal team.
Why did you choose this company over other providers you considered?
The quality of the questions they asked during the briefing process was the first indicator. Vendors who ask precise questions in the sales phase tend to apply the same rigour during delivery. That hypothesis proved accurate. The technical proposal was substantive, the team structure was senior throughout, and the pricing was transparent.
How clearly did the company understand your requirements and business goals?
Better than we managed ourselves going in. The workshops they facilitated surfaced assumptions we had not examined and exposed three requirements that were in direct conflict with each other. Resolving those before development began saved us what would certainly have been significant rework later in the project.
How was your overall experience with their communication and project management?
Outstanding. The discipline around asynchronous communication was particularly effective given the time zones involved between São Paulo, Brazil and the delivery team. Written updates were specific and consistent, response times were same-day for anything that required a decision, and nothing fell through the cracks across a six-month engagement.
Did the company deliver the project on time and within your expected budget?
Yes to both. There was a single sprint where a dependency on a third-party API introduced a one-week delay. The team identified it three weeks in advance, presented two mitigation options, and we agreed on an approach that recovered the schedule within the same sprint cycle. That level of foresight is what separates good project management from reactive problem management.
What tangible results or business impact have you seen since the project was completed?
The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.
What did you like most about working with this company?
The post-launch behaviour. Some vendors consider go-live to be the end of their professional obligation. This team treated it as the transition to a different kind of engagement. The hypercare period was substantive, the documentation was thorough and genuinely useful, and they checked in proactively at the thirty-day and ninety-day marks to review production metrics with us.
Would you recommend this company to others, and would you work with them again?
Yes. I would add the context that this is not the cheapest option in the market and they are selective about the engagements they take on. If your primary criterion is price, there are alternatives. If you want a technology partner who can be trusted with a complex UI/UX Design programme in the Insurance space and will deliver against a serious brief, this is the team.

Company Info

Founded 2009
Employees 50 - 249
Hourly Rate $100 - $149
Client Rating 4.7/5 (6 reviews)

Rating Breakdown

Quality
4.8
Schedule
4.8
Cost
4.8
Communication
4.7

FAQs

How do I actually get a real proposal out of Codal instead of a generic reply?
The most reliable route is giving Codal a clear, specific brief up front — through their website form, a direct email, or a call — since a vague ask tends to get a vague answer back, while a concrete one usually gets a proper estimate. For context, its listed capabilities span Mobile App Development, UI-UX Design and Wearable App Development, and it has been operating since 2009.
What should I expect to pay to work with Codal?
What Codal charges comes down to a handful of variables — how complex the project is, the number of development hours involved, the tech stack required, team size, and which engagement model you pick. Based on available data, Codal's typical hourly rate is around $100 - $149, with an average project cost of $2500000+.
Will Codal sign an NDA before we even discuss the project in detail?
Most professional shops, including Codal, expect to sign a Non-Disclosure Agreement before getting into specifics — it's a fairly standard ask and a reasonable one to make before sharing anything sensitive. For context, it has served clients in USA, and it reports a team size of 50 - 249 professionals.
What kinds of industries has Codal actually built for?
Codal has delivered projects across a range of different industries, including Energy & Utilities, Gaming & Gambling, Nonprofit & NGO, Sports & Fitness, Insurance and Advertising & Marketing.
Does Codal only work locally, or take on clients elsewhere too?
Codal isn't necessarily limited to one region and may take on clients across several countries, including USA, depending on market demand and business partnerships.
Is Codal more of an offshore setup or a local team?
That depends on where Codal is based and who they primarily serve — some firms like this operate fully offshore, some are local-first, and plenty run a hybrid model that mixes both. For context, it has served clients in USA, and it has experience across industries such as Energy & Utilities, Gaming & Gambling, Nonprofit & NGO, Sports & Fitness, Insurance and Advertising & Marketing.
Has Codal actually shipped a SaaS product before?
It's a common line of work for a company like Codal — multi-tenant architecture, subscription billing hooked up properly, and cloud-native deployment built for a product meant to scale as a service rather than a one-off build. For context, it has experience across industries such as Energy & Utilities, Gaming & Gambling, Nonprofit & NGO, Sports & Fitness, Insurance and Advertising & Marketing, and it has been operating since 2009.
Roughly how long does a project with Codal take start to finish?
It depends heavily on scope. A lean MVP might be a matter of weeks, while a full enterprise system or a larger digital transformation project can stretch into months once you factor in development, testing, and deployment. With a team of 50 - 249 professionals, Codal can scale resources based on project urgency.
What does Codal's actual delivery process look like week to week?
Codal generally runs something close to a standard structured process — requirements gathering, UI/UX design, development in agile sprints, QA testing along the way, deployment, and support once it's live. For context, it has experience across industries such as Energy & Utilities, Gaming & Gambling, Nonprofit & NGO, Sports & Fitness, Insurance and Advertising & Marketing, and it has been operating since 2009.