About AnalogFolk
They create relevant brand practices that help people reach their goals. Their mission is to utilize digital to make the analog world best. They believe that interactive experiences are the most satisfying as they affect people. So they make and market interactive experiences that make value for people & brands.
Services
AnalogFolk Reviews
Write a ReviewTechnically rigorous, commercially grounded, and a genuine pleasure to work with
Zara Hussain / Head of Technology - Ravi Digital AgencyMay 23, 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.
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
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
A technology investment that delivered returns ahead of the business case we approved
Eoghan Fitzgerald / VP of Engineering - Shannon Tech Solutions LtdMay 08, 2026
Project summary: Multi-touch attribution across our media mix had become the most-requested capability from every client in our portfolio. We could not deliver it without rebuilding our data layer.
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.
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
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
Questions & Answers
Accessibility-first approach that broadened our audience and impressed our enterprise clients
Dominic Fairfax / Head of Digital Transformation - Arcadian Consulting LtdApr 30, 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.
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.
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
Smart infrastructure project that paid back the investment in under two quarters
Fatima Al-Suwaidi / Head of Digital Strategy - Gulf FinTech HoldingsApr 30, 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 thing that retrospectively seems most significant is how little drama there was. Complex technology projects tend to accumulate incidents, escalations, and tense conversations. This one did not. Problems were surfaced before they became incidents. Scope changes were handled with process rather than conflict. Risks were managed rather than avoided. That level of maturity is rare in my experience and it made the delivery feel almost effortless from our side, which I know it was not from theirs.
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
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
Architecture review that saved us from a vendor decision we would have regretted for years
Radosław Kowalczyk / Head of Development - Wisła Software Sp zooApr 11, 2026
Project summary: Matter management had become a significant overhead for our fee earners. Every hour spent on administration was an hour not spent on billable advisory work — the business case was straightforward.
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.
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
A studio team who played the game obsessively and built it accordingly
Gustavo Ferreira / VP of Technology - Amazônia Digital LtdaMar 18, 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.
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.
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
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
Smart contracts delivered with the rigour and security our compliance team demanded
Maximilian Schreiber / Director of IT - Schreiber Logistik GmbHDec 11, 2025
Project summary: The project had both a hard delivery date tied to a board commitment and a scope that our previous agency had told us was not achievable. We needed someone to prove otherwise.
I have worked with development agencies on four continents over the past fifteen years and this team sits comfortably in the top tier. What separated them was not just technical skill, which was genuinely impressive, but their instinct for asking the right business questions before reaching for a technical answer. The project ran to schedule, the architecture is clean and well-documented, and the handover was thorough. Six months after go-live we have not raised a single critical support ticket. That speaks for itself.
Technical depth across the full stack, honest and timely communication, delivered exactly what was scoped without surprise additions to the invoice
Premium pricing compared to some of the alternatives we evaluated, but the quality of the output and the absence of rework costs made the investment straightforward to justify
Questions & Answers
The team spoke the language of both data science and business — rare combination
Piotr Wojciechowski / Head of Development - Vistula Software Sp zooSep 11, 2022
Project summary: Peak season traffic had been exposing architectural weaknesses in our platform for two years. We could no longer afford to enter a promotional period hoping for the best.
Our industry has specific compliance requirements that many generalist agencies struggle with. This team came with working knowledge of the relevant frameworks, asked pointed questions about our obligations, and built controls into the architecture rather than bolting them on at the end. Our compliance team reviewed the delivered system and had only minor observations, which is genuinely unusual for a first-pass review. That domain awareness saved us significant remediation cost.
Technical depth across the full stack, honest and timely communication, delivered exactly what was scoped without surprise additions to the invoice
Premium pricing compared to some of the alternatives we evaluated, but the quality of the output and the absence of rework costs made the investment straightforward to justify
Questions & Answers
Headless commerce build that gave our marketing team full creative control
Karolina Dabrowska / CTO - Krakow Tech StudioJun 25, 2022
Project summary: Our hospital network required a unified patient data platform that could integrate with existing EMR systems while meeting all relevant data protection obligations.
Project governance was one of the things that impressed me most. We had a dedicated project manager who ran tight fortnightly sprints with clear acceptance criteria, a shared backlog that gave us full visibility at all times, and a change request process that was fair and transparent. Nothing slipped through the cracks, no bill shock at the end, and the final delivery matched the original scope document almost perfectly. In my experience that kind of discipline is genuinely uncommon.
Senior engineers on our account throughout the entire project rather than a bait-and-switch to juniors after contract signing, transparent reporting, realistic estimates that proved accurate
Time zone difference required some adjustment to our internal communication habits but the team managed the overlap window efficiently and it never affected momentum
Questions & Answers
User research that uncovered problems we did not know our customers had
Lachlan Burgess / Chief Digital Officer - Harbour Digital Pty LtdApr 28, 2022
Project summary: The project had both a hard delivery date tied to a board commitment and a scope that our previous agency had told us was not achievable. We needed someone to prove otherwise.
Twelve weeks from kickoff to live production deployment for a project of this complexity. I would not have believed that was achievable if I had not watched them do it. The velocity came from genuine engineering discipline — clear requirements, short feedback loops, automated testing, and a team that communicated internally without the overhead that slows most agencies down. The product has been live for four months with no critical bugs and one minor patch. We are already in scoping conversations for phase two.
Collaborative working style that made them feel like an extension of our team, excellent written communication for our async timezone relationship, clean and readable codebase
We underestimated the internal resource commitment required on our side during discovery — the team warned us, we did not listen fully, and the first sprint was slower as a result