About Friends of The Web
Friends of The Web is a software development company that turns ideas into working products. The company's main offerings are UI/UX Design and Web Development. With 2 - 9 people on staff, Friends of The Web can take on projects of varying size. Projects are generally billed around $200 - $300 / hr/hr. Friends of The Web operates out of Baltimore, MD. These details offer a useful starting point when evaluating Friends of The Web.
Where We Specialize
Industry Expertise
Typical Project Size
Friends of The Web Reviews
Write a ReviewSecurity team that communicated findings clearly to non-technical stakeholders — genuinely rare
Maja Söderström / Head of Product Engineering - Scandia Digital ABApr 27, 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 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.
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
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
Data platform that turned five years of siloed records into a unified analytical asset
Matthieu Renard / Directeur Technique - Lumière Technologies SASApr 06, 2026
Project summary: Our campaign management workflow had grown to involve twelve different tools and significant manual reconciliation. The inefficiency was affecting both speed and accuracy.
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.
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
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
Questions & Answers
An honest assessment of where we were, followed by a credible plan for where we needed to go
Danielle Westbrook / Chief Digital Officer - BlueSky Retail HoldingsMar 17, 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.
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.
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
QA coverage that finally made Friday deployments feel like a professional activity
Marcus Holloway / SVP of Engineering - Vertex Cloud DynamicsMar 16, 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.
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
Performance-first web development that Google Core Vitals confirmed was the right approach
Zara Hussain / Head of Technology - Ravi Digital AgencyFeb 18, 2026
Project summary: As a technology business ourselves we apply the same scrutiny to our vendor selection that our clients apply to us. We needed a delivery partner who could meet a standard we would be comfortable being measured against.
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.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
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
Compliance programme delivered on time and approved by the regulator without remediation
Aarav Mehta / Chief Data Officer - Zenith FinServ LtdJan 13, 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.
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.
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