[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-category-company":3,"blog-category-posts-company":9,"blog-categories":53,"blog-tags":75},{"category":4,"error":8},{"name":5,"slug":6,"description":7,"seo":8},"Company","company","Updates from DrieVerse Tech: what we are building, shipping and learning.",null,{"posts":10,"pagination":49,"error":8},[11,35],{"id":12,"title":13,"slug":14,"excerpt":15,"cover":16,"coverAlt":20,"datePublished":21,"dateModified":21,"category":22,"author":23,"tags":26},"n6ngi38hl6ob37b8x686x6i4","What We Look for in a Discovery Call Before We Say Yes to a Project","what-we-look-for-in-a-discovery-call","A discovery call is a two-way evaluation. Here is what we are actually listening for, and why some conversations end with us recommending someone else.",{"url":17,"width":18,"height":19,"alt":20},"https:\u002F\u002Fmedia.drieverse.com\u002Fdrieverse-media\u002Fcms\u002Fwhat_we_look_for_in_a_discovery_call_cover_83f12dbabe.png",1200,630,"What We Look for in a Discovery Call Before We Say Yes to a Project - cover image (seed-blog-content-cover)","2026-09-05",{"name":5,"slug":6},{"name":24,"slug":25},"DrieVerse Tech","drieverse-tech",[27,29,31,33],{"name":28,"slug":28},"discovery",{"name":30,"slug":30},"positioning",{"name":32,"slug":32},"risk-management",{"name":34,"slug":34},"human-in-the-loop",{"id":36,"title":37,"slug":38,"excerpt":39,"cover":40,"coverAlt":42,"datePublished":21,"dateModified":21,"category":43,"author":44,"tags":45},"wu89fn1m33vz7tvy7etchmei","Why We Publish Case Studies Instead of Testimonials","why-we-publish-case-studies-instead-of-testimonials","A testimonial tells you someone was happy. A case study tells you what was actually built and what happened. Here is why we default to the second one.",{"url":41,"width":18,"height":19,"alt":42},"https:\u002F\u002Fmedia.drieverse.com\u002Fdrieverse-media\u002Fcms\u002Fwhy_we_publish_case_studies_instead_of_testimonials_cover_2d847defc6.png","Why We Publish Case Studies Instead of Testimonials - cover image (seed-blog-content-cover)",{"name":5,"slug":6},{"name":24,"slug":25},[46,48],{"name":47,"slug":47},"evidence-based-claims",{"name":30,"slug":30},{"page":50,"pageSize":51,"pageCount":50,"total":52},1,12,2,[54,58,62,63,67,71],{"name":55,"slug":56,"description":57,"seo":8},"AI and Automation","ai-and-automation","Applied AI and automation: what it actually does inside a working system, and where a human stays in the loop.",{"name":59,"slug":60,"description":61,"seo":8},"Brand and Design","brand-and-design","Visual identity and interface design, and how a consistent design system holds together across a product.",{"name":5,"slug":6,"description":7,"seo":8},{"name":64,"slug":65,"description":66,"seo":8},"Engineering","engineering","Software architecture, code quality and the engineering practice behind the systems we build.",{"name":68,"slug":69,"description":70,"seo":8},"Growth","growth","Search visibility, content and acquisition: the growth work that sits alongside a build rather than bolted onto it.",{"name":72,"slug":73,"description":74,"seo":8},"Infrastructure and Operations","infrastructure-and-operations","DevOps, hosting, reliability and the operational work that keeps a system running once it is live.",[76,78,80,81,82,83,85,86,88,89],{"name":77,"slug":77},"architecture",{"name":79,"slug":79},"decision-frameworks",{"name":28,"slug":28},{"name":47,"slug":47},{"name":34,"slug":34},{"name":84,"slug":84},"observability",{"name":30,"slug":30},{"name":87,"slug":87},"process-design",{"name":32,"slug":32},{"name":90,"slug":90},"technical-debt"]