<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dev to Agency</title><link>https://www.devtoagency.com/</link><description>Dev to Agency helps developers start and run successful software development agencies. Focusing on full-stack devs building high quality custom software for clients.</description><atom:link href="https://www.devtoagency.com/rss.xml" rel="self" type="application/rss+xml"/><item><title>👋</title><link>https://www.devtoagency.com/so-long-and-thanks-for-all-the-whatevers/</link><guid isPermaLink="false">6656772cfe76a20001500712</guid><pubDate>Wed, 29 May 2024 01:01:54 GMT</pubDate><description>Three years ago this month I started Dev to Agency... whoa, that's a long time. Originally this was a place for me to decompress... to work through my thoughts and feelings after selling my agency (while taking 12 months off to travel Australia). But I slowly realised I enjoyed sharing the knowledge I had learned (the hard way!), and I built a nice community around it. It then turned into a place for me to find consulting gigs - and through this blog (and newsletter) I helped a lot of d</description><content:encoded>&lt;p&gt;Three years ago this month I started Dev to Agency... whoa, that&amp;#39;s a long time.&lt;/p&gt;
&lt;p&gt;Originally this was a place for me to decompress... to work through my thoughts and feelings after selling my agency (while taking 12 months off to travel Australia).&lt;/p&gt;
&lt;p&gt;But I slowly realised I enjoyed sharing the knowledge I had learned (the hard way!), and I built a nice community around it.&lt;/p&gt;
&lt;p&gt;It then turned into a place for me to find consulting gigs - and through this blog (and newsletter) I helped a lot of dev agencies, they helped me, and that was a win.&lt;/p&gt;
&lt;p&gt;Those who have been subscribed for a while will probably have noticed the &lt;strong&gt;significant&lt;/strong&gt; lack of recent posts, and those who subscribed recently may have been disappointed about the radio silence. Sorry about this.&lt;/p&gt;
&lt;p&gt;My new startup &lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt; is gaining traction and now needs my full attention - as I want my next five to ten years to be about building an amazing SaaS product - that&amp;#39;s my next challenge.&lt;/p&gt;
&lt;p&gt;Realistically, I won&amp;#39;t be posting any more... at least for the foreseeable future.&lt;br&gt;I feel I&amp;#39;ve said what I needed to say, and the content will remain up, as the majority of these learnings are timeless, and I hope they can help people along their path.&lt;/p&gt;
&lt;p&gt;All the best to everyone, thanks for everything.&lt;/p&gt;
&lt;p&gt;Now let&amp;#39;s all go out there and smash it 🚀&lt;/p&gt;
&lt;p&gt;- Chris&lt;/p&gt;
</content:encoded></item><item><title>Your clients need something</title><link>https://www.devtoagency.com/your-clients-need-something/</link><guid isPermaLink="false">660289961bfaa7000149e517</guid><pubDate>Tue, 26 Mar 2024 09:11:34 GMT</pubDate><description>The world has changed. AI is no longer a futuristic concept confined to science fiction movies, it's here, it's powerful, it's accessible, and improving by leaps-and-bounds every month (or day?) In 2024, millions of businesses - small, medium, and large - will be turning to their software development providers for one thing: AI. Your Clients Need Something This Year - and it's AI ✨ Businesses are looking to understand how AI can provide them with value, and how to start planning an AI strate</description><content:encoded>&lt;p&gt;The world has changed. AI is no longer a futuristic concept confined to science fiction movies, it&amp;#39;s here, it&amp;#39;s powerful, it&amp;#39;s accessible, and improving by leaps-and-bounds every month (or day?)&lt;/p&gt;
&lt;p&gt;In 2024, millions of businesses - small, medium, and large - will be turning to their software development providers for one thing: AI.&lt;/p&gt;
&lt;h2 id=&quot;your-clients-need-something-this-yearand-its-ai-%E2%9C%A8&quot;&gt;Your Clients Need Something This Year - and it&amp;#39;s AI ✨&lt;/h2&gt;
&lt;p&gt;Businesses are looking to understand how AI can provide them with value, and how to start planning an AI strategy. I know this for a fact, as I have helped multiple businesses with this recently.&lt;/p&gt;
&lt;p&gt;They want advice on how AI can help their business run more effectively, efficiently, or to save costs. It’s up to us as development vendors to ensure we are across this, and can advise and implement the tools and practices needed to support this technical revolution.&lt;/p&gt;
&lt;h2 id=&quot;dont-be-scared-%F0%9F%98%B3&quot;&gt;Don&amp;#39;t be scared 😳&lt;/h2&gt;
&lt;p&gt;I know many software developers and agencies that are reluctant to embrace AI. This may be because they are too busy, it&amp;#39;s too fast moving, the simply because they don&amp;#39;t know where to start.&lt;/p&gt;
&lt;p&gt;But the one thing I know for sure is that we are at a turning point right now... And to be a software professional on the right side of history, I believe you should add AI engineering to your toolbelt, and be able to offer this as a service to your existing clients, and new clients.&lt;/p&gt;
&lt;h2 id=&quot;ai-consulting-guiding-your-clients-%F0%9F%A4%9D&quot;&gt;AI Consulting: Guiding Your Clients 🤝&lt;/h2&gt;
&lt;p&gt;As dev agencies and freelancers, we need to understand the fast-moving AI landscape. We need to know what can be achieved, the safety and ethics involved, and how this can positively impact businesses. This means staying up-to-date with the latest advancements - or at least understanding what&amp;#39;s now possible, attending AI events, meetups, and conferences, and importantly - actively learning and experimenting with new tools and models.&lt;/p&gt;
&lt;p&gt;Businesses (potential clients) are desperate for guidance and advice, they want&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;An expert technologist to help guide them (that can be you)&lt;/li&gt;
&lt;li&gt;Examples of how AI can be used to improve their specific business&lt;/li&gt;
&lt;li&gt;What are the potential risks and challenges right now&lt;/li&gt;
&lt;li&gt;What the future opportunities could be&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I strongly recommend you step up, and make it your responsibility to be able to answer these questions, and to help businesses develop a realistic and achievable AI strategy.&lt;/p&gt;
&lt;h2 id=&quot;ai-augmentation-work-smarter-not-harder-%F0%9F%A4%96&quot;&gt;AI Augmentation: Work Smarter, Not Harder 🤖&lt;/h2&gt;
&lt;p&gt;Beyond consulting, we need to ensure we are leveraging the best AI tools to deliver value better and faster. This isn&amp;#39;t about replacing humans, it&amp;#39;s about augmenting our existing skills and processes.&lt;/p&gt;
&lt;p&gt;Some industry-leading AI tools that can help agencies and freelancers include:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/features/copilot?ref=devtoagency.com&quot;&gt;Github Copilot&lt;/a&gt;: This tool uses AI to suggest code completions and entire functions, which can significantly increase developer productivity.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.wix.com/studio?ref=devtoagency.com&quot;&gt;Wix Studio&lt;/a&gt;: This platform offers AI-powered website creation and management, specifically built for agencies and freelancers&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt;: This AI-powered requirements management platform helps agencies and freelancers gather and manage project requirements more efficiently and effectively.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;These are just a few examples, and new tools are being developed every day. By staying informed and experimenting with these tools, we can find ways to improve our workflows and deliver better results for our clients.&lt;/p&gt;
&lt;h2 id=&quot;ai-implementation-bringing-ai-to-life-%F0%9F%8C%B1&quot;&gt;AI Implementation: Bringing AI to Life 🌱&lt;/h2&gt;
&lt;p&gt;Ultimately, it&amp;#39;s up to us as the builders to implement AI-augmented and AI-forward services and products for our clients. There are so many possibilities, but some examples include&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Building AI-powered chatbots and agents to improve customer service and automate tasks.&lt;/li&gt;
&lt;li&gt;Developing custom software that leverages AI for data analysis and reporting.&lt;/li&gt;
&lt;li&gt;Integrating AI into existing systems to improve efficiency and effectiveness.&lt;/li&gt;
&lt;li&gt;Creating new AI-powered products and services for clients to sell or use internally.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The possibilities are endless, and the potential for innovation is immense. By embracing AI and integrating it into our offerings, we can help our clients achieve their goals and stay ahead of the curve.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;AI is here to stay, and it&amp;#39;s changing the world around us.  &lt;/p&gt;
&lt;p&gt;As development agencies and freelancers, we have a unique opportunity to leverage our skills and expertise to help businesses navigate this new landscape. By embracing AI consulting, augmentation, and implementation, we can add immense value to our clients and ensure our own businesses thrive in the years to come.&lt;/p&gt;
</content:encoded></item><item><title>📙 Book: Client Bytes - Get More Clients</title><link>https://www.devtoagency.com/get-more-clients/</link><guid isPermaLink="false">656edb8cfde8370001a492af</guid><pubDate>Tue, 05 Dec 2023 21:14:57 GMT</pubDate><description>If you want more clients for your dev agency or freelancing business, then I wrote a book for you - it's called Client Bytes - Dev Agency and Freelancer Sales. My good friend Nat [https://twitter.com/natmiletic] (who runs a very successful dev agency in Calgary) co-authored the book to tackle one of the hardest questions... 1. How do I get more clients? 2. Get more work from existing clients? 3. Find the sales and marketing tactics that work best for me? Over 12 months of writing, over</description><content:encoded>&lt;p&gt;If you want more clients for your dev agency or freelancing business, then &lt;strong&gt;I wrote a book for you&lt;/strong&gt; - it&amp;#39;s called Client Bytes - Dev Agency and Freelancer Sales.&lt;/p&gt;
&lt;p&gt;My good friend &lt;a href=&quot;https://twitter.com/natmiletic?ref=devtoagency.com&quot;&gt;Nat&lt;/a&gt; (who runs a very successful dev agency in Calgary) co-authored the book to tackle one of the hardest questions...&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;How do I get more clients?&lt;/li&gt;
&lt;li&gt;Get more work from existing clients?&lt;/li&gt;
&lt;li&gt;Find the sales and marketing tactics that work best for me?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Over 12 months of writing, over 22,000 words, 74 pages of highly actionable content with 37 proven strategies for landing more clients and increasing your business&amp;#39;s awareness.&lt;/p&gt;
&lt;p&gt;Now I&amp;#39;m not a typical salesman type... and it seems super &amp;quot;salesy&amp;quot; to say this... but I&amp;#39;m so confident this book will improve your business that &lt;strong&gt;I&amp;#39;m happy to offer a 100% money-back guarantee.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Oh, and because you are my awesome Dev to Agency friends, you can get &lt;strong&gt;10% off if purchased within the next 7 days&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Click the link below to learn more and purchase.&lt;/p&gt;
&lt;h2 id=&quot;%F0%9F%93%96-client-bytesdev-agency-and-freelancer-sales&quot;&gt;📖 &lt;a href=&quot;https://clientbytes.gumroad.com/l/dev-agency-and-freelancer-sales/newsletter10off?ref=devtoagency.com&quot;&gt;Client Bytes - Dev Agency and Freelancer Sales&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Thanks friends, I&amp;#39;d love to know what you think - so please leave a review on Gumroad 🙂&lt;/p&gt;
&lt;p&gt;Chris.&lt;/p&gt;
</content:encoded></item><item><title>Interview with Clarence Ho from Atlasopen</title><link>https://www.devtoagency.com/interview-with-clarence-ho-from-atlasopen/</link><guid isPermaLink="false">6536f37c92aeaf0001840cb0</guid><pubDate>Mon, 23 Oct 2023 22:58:09 GMT</pubDate><description>Clarence Ho is the director and founder of Atlasopen, a software development company based in Melbourne, Australia - and he's been an entrepreneur for a long time. I've been friends with Clarence for quite a few years, as we used to work out of the same co-working space. He's a great businessman, and I've been looking forward to hearing his story. Can you introduce yourself &amp; Atlasopen to the Dev to Agency readers? Sure, I'm Clarence and I’m the Founder at Atlasopenm and we’re a software dev</description><content:encoded>&lt;p&gt;Clarence Ho is the director and founder of &lt;a href=&quot;https://atlasopen.com/?ref=devtoagency.com&quot;&gt;Atlasopen&lt;/a&gt;, a software development company based in Melbourne, Australia - and he&amp;#39;s been an entrepreneur for a long time.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve been friends with Clarence for quite a few years, as we used to work out of the same co-working space. He&amp;#39;s a great businessman, and I&amp;#39;ve been looking forward to hearing his story.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2023/10/clarence-ho-atlasopen.png&quot; alt=&quot;&quot;&gt;&lt;figcaption&gt;Clarence Ho from Atlasopen&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2 id=&quot;can-you-introduce-yourself-atlasopen-to-the-dev-to-agency-readers&quot;&gt;Can you introduce yourself &amp;amp; Atlasopen to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;Sure, I&amp;#39;m Clarence and I’m the Founder at Atlasopenm and we’re a software development agency based out of Melbourne, Australia.&lt;/p&gt;
&lt;p&gt;Personally, I&amp;#39;ve worked across a spectrum of industries including financial services, superannuation, insurance, health and more. In a previous life, I was working in Melbourne for a Big 4 Accounting Firm but realised it just wasn’t for me so I made the shift to working for myself.&lt;/p&gt;
&lt;p&gt;Raising some start-up capital, I was then able to launch one of Australia’s first fitness/health marketplaces allowing customers to book into studios and clinic’s digitally through a single site.&lt;/p&gt;
&lt;p&gt;I ended up selling this business to an ASX-listed company (the Australian Stock Exchange) and moved on to other ventures, which ended up becoming Atlasopen.&lt;/p&gt;
&lt;h2 id=&quot;how-did-atlasopen-start&quot;&gt;How did Atlasopen start?&lt;/h2&gt;
&lt;p&gt;Back in 2017, we were developing our own mobile chat application for the Apple app store, however, it was difficult to scale and ultimately found out that the chat messaging market was pretty competitive at that time. So it didn&amp;#39;t work out.&lt;/p&gt;
&lt;p&gt;But we then started taking requests for developing apps for start-ups and small businesses as a way to earn revenue, and it just snowballed from there, and Atlasopen was born.&lt;/p&gt;
&lt;h2 id=&quot;do-you-have-a-niche-or-an-ideal-customer-type&quot;&gt;Do you have a niche or an ideal customer type?&lt;/h2&gt;
&lt;p&gt;Yes, we don’t like taking on work too far outside of our wheelhouse.&lt;/p&gt;
&lt;p&gt;Current industries we are focusing on include health and care services, in particular primary care and mental health services.&lt;/p&gt;
&lt;p&gt;We also target government and enterprise clients. This doesn’t mean we exclude everything else, we just focus on acquiring customers in this space, and have built up a good reputation by doing so.&lt;/p&gt;
&lt;h2 id=&quot;how-did-you-find-your-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;How did you find your first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;We first started by talking to our personal network, you’d be surprised how many people in your network want things done. But I still had to put myself out there, and not be afraid to talk to people, follow up, and actually try to sell (not just wait for them to come to me!).&lt;/p&gt;
&lt;h2 id=&quot;what-challenges-did-you-face-early-on-and-how-did-you-overcome-them&quot;&gt;What challenges did you face early on, and how did you overcome them?&lt;/h2&gt;
&lt;p&gt;The biggest challenge I faced early on was understanding the industry, how things worked, how to hire the right people, and learning the landscape and technology to piece it all together.&lt;/p&gt;
&lt;h2 id=&quot;did-you-have-a-clear-vision-of-what-your-business-would-be-when-you-first-started-and-has-that-changed-at-all&quot;&gt;Did you have a clear vision of what your business would be when you first started, and has that changed at all?&lt;/h2&gt;
&lt;p&gt;It wasn’t clear where the business would be in 3, 5 or 10 years at all, and it has certainly changed over time.&lt;/p&gt;
&lt;p&gt;In the early days, it was about ensuring that we could earn enough to make a living and not so much about developing a sustainable scalable business.&lt;/p&gt;
&lt;p&gt;But over time, with some wins but also many losses, we were able to work with enough clientele to become proficient and professional enough to develop top-end software for enterprise and government.&lt;/p&gt;
&lt;p&gt;This took a lot of time and effort and it certainly didn’t happen overnight.&lt;/p&gt;
&lt;p&gt;From here, we are in the process of scaling out our own platform for current and future customers that solves their biggest challenges.&lt;/p&gt;
&lt;h2 id=&quot;what-challenges-do-you-face-today&quot;&gt;What challenges do you face today?&lt;/h2&gt;
&lt;p&gt;Challenges come from all places, the technology landscape is evolving perhaps the fastest it’s ever been, customers are more demanding than ever before and attracting and retaining staff is about the hardest it has ever been.&lt;/p&gt;
&lt;p&gt;However, there is also a lot of opportunity with AI moving the world rapidly into the new era, there will be change for the good (and no doubt the bad too).&lt;/p&gt;
&lt;h2 id=&quot;what-do-you-think-sets-atlasopen-apart-from-other-agencies&quot;&gt;What do you think sets Atlasopen apart from other agencies?&lt;/h2&gt;
&lt;p&gt;Atlasopen has an innovative culture that fosters continuous learning and innovation which helps us stay ahead of the curve.&lt;/p&gt;
&lt;p&gt;This is very important for a software development company, as we want to grow with our clients, and be able to offer them the best services possible.&lt;/p&gt;
&lt;h2 id=&quot;what-do-you-hope-your-business-looks-like-in-3-years&quot;&gt;What do you hope your business looks like in 3 years?&lt;/h2&gt;
&lt;p&gt;From here, we are actively pushing our new enterprise product that we have already rolled out to some of our customers who reside in the healthcare and care services space.&lt;/p&gt;
&lt;p&gt;We will be focused on scaling our ‘platform’ business over the coming 3 years which we anticipate will equal and exceed our services business revenue within this timeframe.&lt;/p&gt;
&lt;h2 id=&quot;what-are-3-things-you-would-tell-a-developer-who-is-thinking-of-starting-a-software-agency&quot;&gt;What are 3 things you would tell a developer who is thinking of starting a software agency?&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Get in touch with people who have experience in the space&lt;/li&gt;
&lt;li&gt;Hire the right people, as your business relies on them&lt;/li&gt;
&lt;li&gt;Find the right mentors who can help you along your journey&lt;/li&gt;
&lt;/ol&gt;
</content:encoded></item><item><title>Leverage your superpower</title><link>https://www.devtoagency.com/leverage-your-superpower/</link><guid isPermaLink="false">650a3203feecc500014ff069</guid><pubDate>Tue, 19 Sep 2023 23:57:05 GMT</pubDate><description>There are a million things you need to focus on in an agency, and recently I wrote an article about wearing many hats [https://www.devtoagency.com/wearing-many-hats/] around how learning to do lots of things is a superpower in your agency. This is because it’s what worked for me, and helped me grow a 7-figure business in a couple of years. By learning many new skills fast while staying small and lean. But running your own business needs to be about doing what you want, and I speak to many agen</description><content:encoded>&lt;p&gt;There are a million things you need to focus on in an agency, and recently I wrote an article about &lt;a href=&quot;https://www.devtoagency.com/wearing-many-hats/&quot;&gt;wearing many hats&lt;/a&gt; around how learning to do lots of things is a superpower in your agency.&lt;/p&gt;
&lt;p&gt;This is because it’s what worked for me, and helped me grow a 7-figure business in a couple of years. By learning many new skills fast while staying small and lean.&lt;/p&gt;
&lt;p&gt;But running your own business needs to be about doing what you want, and I speak to many agency owners who don’t want to end up wearing “all the hats” - and that’s totally fine.&lt;/p&gt;
&lt;p&gt;Instead, you can focus on what you do best, where you have the most impact, and what you enjoy the most. This is your superpower.&lt;/p&gt;
&lt;p&gt;Whether your superpower is software development, UI/UX design, sales and marketing, or whatever - there are ways to optimize your time on these tasks and leverage them to build your business.&lt;/p&gt;
&lt;p&gt;Let’s be honest - there’s no way you can &lt;em&gt;just&lt;/em&gt; be a software developer who codes 100% of the time and also runs an agency. That’s an employee.&lt;/p&gt;
&lt;p&gt;But you can use strategies to ensure you spend the most possible time doing what you do best -  let’s run through a few of those.&lt;/p&gt;
&lt;h2 id=&quot;leverage-you-niche-%F0%9F%8E%AF&quot;&gt;Leverage you niche 🎯&lt;/h2&gt;
&lt;p&gt;Working on every project that comes along can work well to get started, but being a “jack of all trades” comes with its overheads, whereas &lt;a href=&quot;https://www.devtoagency.com/think-niche/&quot;&gt;having a niche&lt;/a&gt; can reduce some of those.&lt;/p&gt;
&lt;p&gt;A lot of times an agency revolves around sales, marketing, and building a brand - because this is how you get work.&lt;/p&gt;
&lt;p&gt;But what if instead, people came to you because you were the #1 expert in your specific field?&lt;/p&gt;
&lt;p&gt;And the more projects you get of that certain type, the better and more efficient you get at it, and the more clients are blown away by your agency&amp;#39;s awesomeness, the more they cannot help but come back to you and recommend you to everyone they know.&lt;/p&gt;
&lt;p&gt;Building a niche is not something that happens overnight, you can’t avoid putting in the initial work, but long term it can reduce your sales and marketing efforts, increase your referral rate, increase your profits, and optimize the time you spend delivering projects, not searching for them.&lt;/p&gt;
&lt;h2 id=&quot;leverage-humans-%F0%9F%A7%8D%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;Leverage humans 🧍‍♀️&lt;/h2&gt;
&lt;p&gt;Outsourcing or insourcing is another way to ensure you stay focused on what you do best.&lt;/p&gt;
&lt;p&gt;There are hundreds of tasks that other humans will be better at than you, but just make sure you&amp;#39;re not delegating your competitive advantage to someone else. For example, if you’re awesome at paid advertising and lead conversation, that’s probably not something you want to outsource (unless of course you very specifically train someone on your methods).&lt;/p&gt;
&lt;p&gt;There are hundreds of tasks that other humans will be better at than you, some include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Hiring an accountant to do your taxes&lt;/li&gt;
&lt;li&gt;Hiring a sales and marketing team to create and implement paid advertising&lt;/li&gt;
&lt;li&gt;Hiring a tester to help with quality assurance&lt;/li&gt;
&lt;li&gt;Outsource basic website creation to a freelancer (yes, even if you’re a programmer you can focus on the more impactful code!)&lt;/li&gt;
&lt;li&gt;Outsourcing copywriting to a freelancer&lt;/li&gt;
&lt;li&gt;Outsourcing graphic design to a freelancer&lt;/li&gt;
&lt;li&gt;Delegating admin tasks to another team member&lt;/li&gt;
&lt;li&gt;Delegating admin tasks to a virtual assistant&lt;/li&gt;
&lt;li&gt;Delegating all client inquiries, lead followups, and sales funnel tasks to a virtual assistant&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;leverage-tools-%F0%9F%9B%A0%EF%B8%8F&quot;&gt;Leverage tools 🛠️&lt;/h2&gt;
&lt;p&gt;A great way to save time on tasks is via automation and optimization - and computers are awesome at both of those.&lt;/p&gt;
&lt;p&gt;There are a ridiculous amount of tools at your disposal here, but some that I use include…&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://chat.openai.com/?ref=devtoagency.com&quot;&gt;ChatGPT&lt;/a&gt; for everything 🙂&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.xero.com/?ref=devtoagency.com&quot;&gt;Xero&lt;/a&gt; to get your accounts in order, keep track of finances, and cut down the time your accountant needs to lodge your taxes&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://tweethunter.io/?ref=devtoagency.com&quot;&gt;Tweethunter&lt;/a&gt; and &lt;a href=&quot;https://taplio.com/?ref=devtoagency.com&quot;&gt;Taplio&lt;/a&gt; to automate your social media, and get great content inspiration&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.wix.com/studio?ref=devtoagency.com&quot;&gt;WixStudio&lt;/a&gt; to create and manage websites, specifically built for agencies and freelancers with some pretty amazing AI&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.apollo.io/?ref=devtoagency.com&quot;&gt;Apollo.io&lt;/a&gt; for lead generation and email automation&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://calendly.com/?ref=devtoagency.com&quot;&gt;Calendly&lt;/a&gt; allows people to book meetings that fit everyone’s schedule, avoids ten emails trying to find a suitable time&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.loom.com/?ref=devtoagency.com&quot;&gt;Loom&lt;/a&gt; can easily record and host video for asynchronous and repeatable communication or training&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://zapier.com/?ref=devtoagency.com&quot;&gt;Zapier&lt;/a&gt; and &lt;a href=&quot;http://make.com/?ref=devtoagency.com&quot;&gt;Make.com&lt;/a&gt; can automate all the things&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt; for software requirements management and automation with AI (shameless plug!)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;leverage-documentation-%F0%9F%93%9A&quot;&gt;Leverage documentation 📚&lt;/h2&gt;
&lt;p&gt;If you don’t want to do something again, then write down how you did it, and next time you can get someone else to do it. Simple.&lt;/p&gt;
&lt;p&gt;It’s amazing how many people don’t do this, but seriously, this is how businesses scale - and if you are a one-man-show documentation will allow you to outsource and onboard a lot ****easier. Plus it’s an investment in stopping a lot of future questions you will be asked such as “What do we do when X happens?”&lt;/p&gt;
&lt;p&gt;Examples of what you can document…&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your lead conversion steps - what you do when you have a new lead (e.g. tell them about Y, ask about X etc.)&lt;/li&gt;
&lt;li&gt;Standard client contract&lt;/li&gt;
&lt;li&gt;Your client onboarding steps - what to do when your lead becomes a customer (e.g. send them through the client contract to sign via DocuSign, set them up in Notion, Jira, Xero - whatever)&lt;/li&gt;
&lt;li&gt;New hire onboarding steps - this is how we work, this is where we keep our code, this is where we keep our requirements, this is where we keep our shared passwords, etc.&lt;/li&gt;
&lt;li&gt;Coding standards - we use tabs (or spaces), we leverage this coding standard (e.g. &lt;a href=&quot;https://github.com/airbnb/javascript?ref=devtoagency.com&quot;&gt;AirBnB JS&lt;/a&gt;), we use semantic commit messages, we do PRs using this template etc.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Documentation can seem like a ridiculously large task - but you shouldn’t write it the first time you do a task. Write it the second or third time, so you have time to optimize your process, plus it doesn’t seem like you’re spending all your time documenting.&lt;/p&gt;
&lt;p&gt;An important note with documentation is it’s often easy to write, but hard to maintain.&lt;/p&gt;
&lt;p&gt;You need to embrace continual, living documentation, that just becomes part of your business foundations and creates a living, breathing resource that evolves over time.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Whilst the tactics covered above still take a bunch of work to implement, the payoff is an increase in the time spent on &lt;em&gt;your thing&lt;/em&gt; - your superpower.&lt;/p&gt;
&lt;p&gt;And ultimately, you need to build a business you want to work in.&lt;/p&gt;
</content:encoded></item><item><title>AI and dev agencies</title><link>https://www.devtoagency.com/ai-and-dev-agencies/</link><guid isPermaLink="false">64a0e9ad821c9f0001d821e5</guid><pubDate>Sun, 02 Jul 2023 23:30:48 GMT</pubDate><description>The world has changed, AI is easier to integrate today than ever before - and Dev agencies have a big opportunity.</description><content:encoded>&lt;p&gt;Like a lot of developers, for the last few months all I have been thinking about is AI - and yes - this explains why my posts on Dev to Agency have become fewer in frequency 🙂&lt;/p&gt;
&lt;p&gt;I’ve immersed myself in learning all I can about the new frontier of generative AI, and playing with every tool possible. I pivoted my agency consulting role into AI engineer, and started building tech demos of how gen AI can be used to offer new and improved services to clients and enhance their products way beyond what was previously possible.&lt;/p&gt;
&lt;p&gt;I’m integrating more advanced and richer AI experiences into my requirements management startup &lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt;, and every week I am blown away by what is possible today.&lt;/p&gt;
&lt;p&gt;It’s a freaking exciting time to be a software developer.&lt;/p&gt;
&lt;h2 id=&quot;why-dev-agencies-need-to-pay-attention-to-ai-%E2%9C%A8&quot;&gt;Why dev agencies need to pay attention to AI ✨&lt;/h2&gt;
&lt;p&gt;I ran my software agency when Blockchain was getting big, and when Web3 was going to change the world. But I largely ignored it, and never thought of pitching to my clients how Web3 could help them make money or save money. I felt that when the mass hype died down - it wouldn’t in fact change the world like people thought, and on that point I feel I was correct.&lt;/p&gt;
&lt;p&gt;But with AI and large language models (such as GPT-4), it feels &lt;em&gt;different&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;AI can literally allow us to do things we NEVER could before. It’s not a new way of doing X, or a faster way of doing Y, it’s an entirely new platform that unlocks completely new opportunities.&lt;/p&gt;
&lt;p&gt;Similar to when modern smartphones came out around 2007 - a whole new market segment has just opened up to people who can code and create software.&lt;/p&gt;
&lt;p&gt;If 2 years ago a client asked my agency “Hey Chris, we need to chat to our database using natural language, oh and I also want to see graphs and charts!”&lt;/p&gt;
&lt;p&gt;I guess I would have known *someone out there could probably do it *&lt;strong&gt;-&lt;/strong&gt;  but unless we could find them or a product/API we could leverage, we would have to say “&lt;em&gt;Sorry, this is out of our wheelhouse!&lt;/em&gt;”.&lt;/p&gt;
&lt;p&gt;But I’ve just &lt;a href=&quot;https://twitter.com/chrisrickard/status/1671439674018263048?ref=devtoagency.com&quot;&gt;built this exact thing&lt;/a&gt; in a couple of days, allowing someone to talk to their database (any database) using natural language sentences. Oh, and it supports &lt;a href=&quot;https://twitter.com/chrisrickard/status/1672428195407355904?ref=devtoagency.com&quot;&gt;replying with dynamic graphs and charts&lt;/a&gt; - just like magic.&lt;/p&gt;
&lt;p&gt;And this is just a drop in the ocean of what you can offer to your clients…&lt;/p&gt;
&lt;h2 id=&quot;what-dev-agencies-can-do-today-with-ai-that-they-couldn%E2%80%99t-do-yesterday-%F0%9F%92%A1&quot;&gt;What dev agencies can do today with AI, that they couldn’t do yesterday 💡&lt;/h2&gt;
&lt;p&gt;OpenAI released API public access to GPT3 way back in November 2021, and I know that specialised AI peeps could weave magic for a long time. But I’m focusing on the generalist developer or agency - and what AI and LLMs can allow us to do a lot simpler than ever before.&lt;/p&gt;
&lt;p&gt;The answer to what we can do is essentially endless, but focusing on areas where software development agencies could add value to their clients, here are a few high-level Ideas.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Data mining &amp;amp; semantic search across unstructured datasets&lt;/strong&gt; - whether it’s ad-hoc Word documents or PDFs, emails, or speech-to-text-recorded telephone calls. AI can add structure and summarisation to this “data”, and also look through it to pull out specific details (e.g. “Which of these recorded telephone calls are complaints about products or services?”&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Quick and easy sentiment analysis&lt;/strong&gt; - this could be used for classifying comments, reviews, questionnaires, forms etc. as Positive, Negative, or Neutral. And even providing more context, e.g. “Samantha G’s telephone call was negative, expressing anger and dissatisfaction about the Tesla she purchased in 2022”&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AI Agents&lt;/strong&gt; - Chatbots have been around for ages (with varying degrees of “AI”) - but whereas chatbots “talk” - agents “do”. Agents perform tasks, and actually get shit done. Agents can actually cancel a customer&amp;#39;s subscription, not just tell them how to do it themselves. Agents can actually order you groceries, not just talk about it. Agents are the new generation of chatbots, and agents will be huge.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automated reporting&lt;/strong&gt; - managers want a weekly report email about X,Y,Z - often just to see if everything looks ok. But what if AI sent automated report emails when anomalies happened, not using hardcoded boolean logic, but more natural decisions. “Does this week&amp;#39;s orders seem similar to the last 10 weeks’ orders”, if not perhaps “Generate a small summary of the differences”, and let’s get a manager to check that out (all automated).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Systems integration&lt;/strong&gt; - like my database chatting example previously (that generated valid SQL from natural language), LLMs are amazing at understanding code and syntax. You can give them an API spec and they can generate example integration code. You can give them code, and they can generate a detailed spec. This opens a lot of opportunities for writing dynamic integrations and allowing the LLM to be the middleman.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Content generation&lt;/strong&gt; - I’m not talking about blog posts or product taglines. But boring business content that needs producing. Forms, reports, documents, and even emails. Things businesses spend time on that now could be automated.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;so-what-should-i-do-about-it-%F0%9F%A4%94&quot;&gt;So what should I do about it? 🤔&lt;/h2&gt;
&lt;p&gt;I believe development agencies are in a great position to learn, master, and offer AI services.&lt;/p&gt;
&lt;p&gt;Even though it seems we are at “peak AI excitement” at the moment, we are not.&lt;/p&gt;
&lt;p&gt;As technologists, we see it coming first. Give it a year, maybe two years - and every single business we will want to harness the power of AI for two core reasons that are as old as time.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;To save money&lt;/li&gt;
&lt;li&gt;To make money&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Sure, there will be AI-assisted products and SaaS services to help them, but just like always, organisations have endless business rules and complexity, and many will still need custom software to work exactly the way they need it to.&lt;/p&gt;
&lt;h2 id=&quot;how-do-i-get-started-%F0%9F%8F%83%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;How do I get started? 🏃‍♂️&lt;/h2&gt;
&lt;p&gt;Start learning by playing with AI development tools, AI is moving crazy fast, and every day there are new tools, models, and companies that provide opportunities and inspiration.&lt;/p&gt;
&lt;p&gt;I don’t just mean ChatGPT, I mean tools like &lt;a href=&quot;https://python.langchain.com/docs/get_started/introduction.html?ref=devtoagency.com&quot;&gt;LangChain&lt;/a&gt; and &lt;a href=&quot;https://github.com/yoheinakajima/babyagi?ref=devtoagency.com&quot;&gt;BabyAGI&lt;/a&gt; that let you talk to many different models in many different ways. This is what opens open the power to developers.&lt;/p&gt;
&lt;p&gt;Build small demos, build them for fun, build them to explore what’s possible. It will inspire other ideas and help you get a grasp on the true power available.&lt;/p&gt;
&lt;p&gt;For example, recently I got beta access &lt;a href=&quot;https://www.anthropic.com/product?ref=devtoagency.com&quot;&gt;Anthropic&amp;#39;s Claude&lt;/a&gt; API, which allows you to send 100k worth of tokens in your prompt. I didn’t get the power of this at first, but I now see it. And it’s huge. Being able to send around 75,000 words in your LLM prompt is a game changer, and it’s filled my head with new ideas.&lt;/p&gt;
&lt;p&gt;Find a way that works for you to stay up to date. I listen to &lt;a href=&quot;https://github.com/swyxio/ai-notes/blob/main/Resources/Good%20AI%20Podcasts%20and%20Newsletters.md?ref=devtoagency.com&quot;&gt;AI Podcasts and read AI newsletters&lt;/a&gt; - and follow people in the AI space on Twitter such as &lt;a href=&quot;https://twitter.com/swyx?ref=devtoagency.com&quot;&gt;swyx&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Have fun, exciting times ✨&lt;/p&gt;
</content:encoded></item><item><title>Wearing many hats</title><link>https://www.devtoagency.com/wearing-many-hats/</link><guid isPermaLink="false">6424b9d3997bb700012d81e0</guid><pubDate>Wed, 29 Mar 2023 22:40:50 GMT</pubDate><description>As an agency owner, one of the biggest challenges is having to juggle multiple tasks and responsibilities - wearing many hats. Unlike larger companies with specialized departments, as a small business owner, you are responsible for everything from development, sales and marketing, accounting, and customer service - you have to wear many hats. Some people hate this. Some people love this. I see it as a necessary part of getting your business off the ground, and if you do it well, you may not</description><content:encoded>&lt;p&gt;As an agency owner, one of the biggest challenges is having to juggle multiple tasks and responsibilities - wearing many hats.&lt;/p&gt;
&lt;p&gt;Unlike larger companies with specialized departments, as a small business owner, you are responsible for everything from development, sales and marketing, accounting, and customer service - you have to wear many hats.&lt;/p&gt;
&lt;p&gt;Some people hate this.&lt;/p&gt;
&lt;p&gt;Some people love this.&lt;/p&gt;
&lt;p&gt;I see it as a necessary part of getting your business off the ground, and if you do it well, you may not need to wear all those hats forever (if you don’t want to).&lt;/p&gt;
&lt;p&gt;This is not SEO targeted AI generated clickbait article, where I tell you how to manage your time, juggle tasks, and stay focused - there are a billion of those articles on the net &lt;a href=&quot;https://letmegooglethat.com/?q=Wearing+many+hats+in+your+business+effectively&amp;amp;ref=devtoagency.com&quot;&gt;if you want to google them&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;wearing-many-hats-is-your-superpower&quot;&gt;Wearing many hats is your superpower&lt;/h2&gt;
&lt;p&gt;In the early years of my agency, half of my clients were solo founders trying to build their startups - by paying others quite a lot of money to do so.&lt;/p&gt;
&lt;p&gt;They could drop anywhere from $15k to $500k just getting their idea developed, and then another $XYZ on sales and marketing when they realise building it’s the &lt;em&gt;easy part&lt;/em&gt; - the hard part is getting a steady stream of paying customers.&lt;/p&gt;
&lt;p&gt;If they were successful in getting some initial traction - and hopefully they were - best case scenario they had to keep paying my agency to add new features and evolve as they pivot and try and find product-market fit. And this could still cost tens of thousands of dollars every year, for many years.&lt;/p&gt;
&lt;p&gt;But If you can personally build something, attract customers, sell to those customers, deliver to those customers, and build a good ongoing relationship for future work - you are in the 0.01% of people in the world who can successfully do this.&lt;/p&gt;
&lt;h2 id=&quot;wear-more-of-the-right-hats&quot;&gt;Wear more of the right hats&lt;/h2&gt;
&lt;p&gt;If you don’t have any idea on how to do SEO, but you’re building websites for clients and confident this is a skill that will add value, and add to your bottom line - then make a point of filling your knowledge gap and go and learn that shit yourself.&lt;/p&gt;
&lt;p&gt;Investing in yourself (and your superpowers) will compound over the years as you become an unstoppable force, and add more and more skills to your arsenal.&lt;/p&gt;
&lt;p&gt;New technology can feel endless…&lt;/p&gt;
&lt;p&gt;You don’t need to learn every new framework or buzzword javascript library - be strategic about what skills will allow you to go &lt;em&gt;deeper&lt;/em&gt;, and serve your customers better.&lt;/p&gt;
&lt;p&gt;It’s &lt;em&gt;possible&lt;/em&gt; that this is web3 or AI.&lt;/p&gt;
&lt;p&gt;But realistically, unless you wear these hats already - it’s probably more like sales and marketing.&lt;/p&gt;
&lt;h2 id=&quot;the-hats-i-wear&quot;&gt;The hats I wear&lt;/h2&gt;
&lt;p&gt;I started as a developer. Didn’t care about anything else but code, it’s all I wanted to do - night and day.&lt;/p&gt;
&lt;p&gt;I went from junior to mid, to senior, to technical lead.&lt;/p&gt;
&lt;p&gt;I built wider skills in client relations, team relations, management, communication, estimation, automated testing -  everything from frontend and backend to middleware and DevOps.&lt;/p&gt;
&lt;p&gt;I left 9-5 work to found a startup with some friends. I learnt about entrepreneurship, business, finance, product-market-fit (or trying to at least!), pitching to investors, working super fucking hard, and eventually - burnout.&lt;/p&gt;
&lt;p&gt;I walked away from my startup and started a development agency. That’s when I really learn about sales, marketing, building a network (professional and personal), long-term client relationships, the balance of quality and cost, building a team, growing a team, partner disputes, acquiring other businesses, and selling my business.&lt;/p&gt;
&lt;p&gt;I then travelled around Australia for a year in an RV, and started Dev to Agency - where I learnt about writing, teaching what you know, idea generation, newsletters, consistency, distribution, Twitter, and building online relationships.&lt;/p&gt;
&lt;p&gt;I’m now working on &lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt; - a startup around AI requirements management, where I’m wearing all the hats I’ve worn over the last 20 years of being in the tech industry.&lt;/p&gt;
&lt;p&gt;But I’m still learning - SaaS pricing, product onboarding, enterprise sales and about 62,000 other things.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;I’m grateful I’ve always pushed myself to keep wearing more hats.&lt;/p&gt;
&lt;p&gt;I haven’t done it all myself, as I’ve built some amazing teams - but only once I’ve proven that role needs to exist (e.g. I did sales and marketing until it was time to hire a team etc).&lt;/p&gt;
&lt;p&gt;It’s about not having to solely rely on others, and being able to get shit done yourself.&lt;/p&gt;
&lt;p&gt;You can build an amazing business wearing many hats - and that can be your superpower.&lt;/p&gt;
</content:encoded></item><item><title>Avoiding Parkinson's Law</title><link>https://www.devtoagency.com/avoiding-parkinsons-law/</link><guid isPermaLink="false">63feee0a8e87090001933565</guid><pubDate>Wed, 01 Mar 2023 22:46:30 GMT</pubDate><description>Parkinson's Law tells us that “work expands to fill the time allotted for its completion” - meaning the more time you have the more time things take. And the origin story is about a woman who had to send a postcard. For many people, that may be a 3-minute task. We are busy, so we don’t want to draw it out. But this woman spends an hour looking for the exact right postcard, another half hour looking for her glasses, 1.5 hours actually writing the card, 20 minutes deciding whether or not to tak</description><content:encoded>&lt;p&gt;Parkinson&amp;#39;s Law tells us that “&lt;em&gt;work expands to fill the time allotted for its completion” -&lt;/em&gt; meaning the more time you have the more time things take.&lt;/p&gt;
&lt;p&gt;And the origin story is about a woman who had to send a postcard.&lt;/p&gt;
&lt;p&gt;For many people, that may be a 3-minute task. We are busy, so we don’t want to draw it out.&lt;/p&gt;
&lt;p&gt;But this woman spends an hour looking for the exact right postcard, another half hour looking for her glasses, 1.5 hours actually writing the card, 20 minutes deciding whether or not to take an umbrella along on her walk to the mailbox etc. In the end, sending a postcard takes her a full day, instead of 3 minutes.&lt;/p&gt;
&lt;p&gt;And I’ve often caught myself falling victim to Parkinson&amp;#39;s Law.&lt;/p&gt;
&lt;p&gt;Give me three days to write a proposal for a client, I can do it.&lt;/p&gt;
&lt;p&gt;Give me one day to write a proposal for a client, I can do it.&lt;/p&gt;
&lt;p&gt;Give me 3 hours to write a proposal for a client, it’s tight.. but you know what? I think I can do it.&lt;/p&gt;
&lt;h2 id=&quot;an-example-of-parkinsons-law&quot;&gt;An example of Parkinson&amp;#39;s Law&lt;/h2&gt;
&lt;p&gt;So you have to choose a technology framework for a new project, a relatively simple project, an online inventory system with an administration interface.&lt;/p&gt;
&lt;p&gt;You’ve previously used NextJS with much success, but lately, you’ve been hearing a lot of talk about Laravel, and are interested in giving it a try. You have 6 weeks until you need to start the next project, so that seems like enough time.&lt;/p&gt;
&lt;p&gt;You can imagine what happens here, where previously you have the core of the project scaffolded in 2 weeks, this time you only accomplish&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Researching Laravel boilerplates, but decide to start from scratch to learn the most&lt;/li&gt;
&lt;li&gt;Learning Docker, as this ships with the default Laravel project and you haven’t used it before&lt;/li&gt;
&lt;li&gt;Trying different authentication packages,  as the ecosystem is huge and there are many options&lt;/li&gt;
&lt;li&gt;Going down a rabbit hole on Laracasts, learning about Pest PHP testing framework&lt;/li&gt;
&lt;li&gt;Getting stuck with PHP syntax, as you haven’t used it for a few years&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;You get the picture.&lt;/p&gt;
&lt;p&gt;You’re not too stressed at the start because you have 6 weeks, but as time rolls on, you&amp;#39;re not where you want to be. Perhaps you bit off more than you can chew. Sure, you learn some new tech, but it’s rushed and stressful - and importantly, even though it seemed like a long time, you ended up going 2 weeks over the 6-week deadline, which ate into the start date of your next project (making that one unnecessarily stressful also).&lt;/p&gt;
&lt;p&gt;Learning is an essential part of life, especially in technology, but it’s important to choose your battles, and understanding our brains - and that Parkinson’s law exists in all of us - can help get your priorities in order.&lt;/p&gt;
&lt;p&gt;For example, you could stick with NextJS, and pump this project out in 4 weeks in your usual high quality in the ecosystem you’re comfortable with. Then you have 2 weeks up your sleeve before your next project - a perfect time to start learning Laravel without any pressure.&lt;/p&gt;
&lt;h2 id=&quot;how-to-avoid-parkinsons-law&quot;&gt;How to avoid Parkinson&amp;#39;s Law&lt;/h2&gt;
&lt;p&gt;If you know humans have a bug, where we “fill the time available” - then we can try and squash this bug. As developers, debugging is what we’re good at right?&lt;/p&gt;
&lt;p&gt;Often it’s easier to debug a piece of code than it is to debug your own behaviours and habits. But to get work done efficiently, and not fill up the time available, these hints might help.&lt;/p&gt;
&lt;h3 id=&quot;1-always-have-a-crystal-clear-scope&quot;&gt;1. Always have a crystal clear scope&lt;/h3&gt;
&lt;p&gt;If you don’t have a plan, you’ll never know if you’re on track.&lt;/p&gt;
&lt;p&gt;Think deeply before coding, and run all edge cases and question past your client in order to agree on what should be done. I capture super detailed user stories and acceptance criteria in &lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt; (yes that’s a shameless plug) and then get my client to approve the requirements even before starting development.&lt;/p&gt;
&lt;p&gt;This helps mitigate the “oh I just realised this…” and “We also need to handle that” which can often occur, and instead makes you more focused on exactly what was agreed.&lt;/p&gt;
&lt;h3 id=&quot;2-estimate-tasks-and-try-and-stay-within-the-range&quot;&gt;2. Estimate tasks, and try and stay within the range&lt;/h3&gt;
&lt;p&gt;Developers traditionally hate estimates, but they serve one good purpose - reminding you how long you &lt;em&gt;thought&lt;/em&gt; the task would take.&lt;/p&gt;
&lt;p&gt;If the postcard-sending lady (in the origin story of Parkinson’s’ law) had estimated the task would take 30 minutes and planned her day around that eventuating - then she wouldn’t have taken 1.5 hours writing the message… or at least she would have had to mentally acknowledge that she’s taking considerably longer than planned.&lt;/p&gt;
&lt;p&gt;It’s ok if things take longer - as long as you are &lt;em&gt;actually&lt;/em&gt; ok with that, and you are mindful about the time spent.&lt;/p&gt;
&lt;p&gt;Timeboxing techniques have worked for centuries to keep you mindful, and methods like &lt;a href=&quot;https://en.wikipedia.org/wiki/Pomodoro_Technique?ref=devtoagency.com&quot;&gt;Pomodoro&lt;/a&gt; have served to get the most out of the time you have and make you more aware of what you are doing right now - compared to what you should be doing.&lt;/p&gt;
&lt;h3 id=&quot;3-do-what%E2%80%99s-most-important-first&quot;&gt;3. Do what’s most important first&lt;/h3&gt;
&lt;p&gt;If the project you’re working on is an AI house blueprint generation platform - where you upload photos of houses and it uses AI to predict what the blueprints and floorplans look like - then just straight into generating the AI blueprints.&lt;/p&gt;
&lt;p&gt;Although starting with the server setup, the DB structure, then the user authentication and admin website etc might seem more of a natural starting progression - it’s not what&amp;#39;s most important… it’s fine to do things out of order and put the important parts first.&lt;/p&gt;
&lt;p&gt;To avoid &lt;em&gt;filling the time available&lt;/em&gt;, you want to start with the most important, most risky components, focusing on getting them up and working as required, but saving any bells and whistles to the end (assuming there’s time that is).&lt;/p&gt;
&lt;h3 id=&quot;4-don%E2%80%99t-get-stuck-on-trivial-edge-cases&quot;&gt;4. Don’t get stuck on trivial edge cases&lt;/h3&gt;
&lt;p&gt;It’s hard to know what’s trivial in a project, as it varies from agency to agency (and client to client), but a good example might be trying to get a website to be pixel-perfect on a super old version of Chrome on Android. Sure, it’s nice to have - but if it’s literally going to affect maybe 0.5% of the users of the website, that should only be something you tackle if the project is delivered perfectly, there are no other improvements, and you’re under time and budget.&lt;/p&gt;
&lt;p&gt;My mentality is to log the small bugs and improvements in your project management tool, but first, get the feature done. I love the saying “&lt;em&gt;make it work make it right make it fast&lt;/em&gt;”.&lt;/p&gt;
&lt;p&gt;You can then triage the issues and decide when and if they need to be dealt with. You don’t want to spend an unplanned day on something that actually adds little value to the project, so always asking yourself “is this trivial?” or “is this a super edge case?” is a good way to detect that it’s occurring.&lt;/p&gt;
&lt;p&gt;Note: I’m not encouraging delivering buggy code by any means, I’m encouraging being self-aware of what’s the most important - and making intentional use of the time you have.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Sometimes it’s fun to spend a couple of days tinkering with new technology, or getting sidetracked going down a stack overflow rabbit hole for a few hours  - and often that’s how we learn and grow.&lt;/p&gt;
&lt;p&gt;But if you’re trying to increase productivity, and trying to hit your project deadlines (whether they are self-enforced or enforced by your clients) - then integrating the techniques above might help you out.&lt;/p&gt;
</content:encoded></item><item><title>My experience with burnout</title><link>https://www.devtoagency.com/my-experience-with-burnout/</link><guid isPermaLink="false">63ec9cd9c5c09500012e059c</guid><pubDate>Thu, 16 Feb 2023 21:45:40 GMT</pubDate><description>Writing an article on the internet about burnout feels a bit like writing about “how to wake up early”, or “eat better and feel great!” - it feels clickbaity and it’s all been said. Am I really that hard-pressed for content? But the truth is, burnout’s a bitch… It hits us differently, at different times, and for different reasons. And the other truth is, agency life (or running any business) can lend itself towards burning out. It can feel like an endless marathon, and even if you “make it”,</description><content:encoded>&lt;p&gt;Writing an article on the internet about burnout feels a bit like writing about “how to wake up early”, or “eat better and feel great!” - it feels clickbaity and it’s all been said. Am I really that hard-pressed for content?&lt;/p&gt;
&lt;p&gt;But the truth is, burnout’s a bitch…&lt;/p&gt;
&lt;p&gt;It hits us differently, at different times, and for different reasons.&lt;/p&gt;
&lt;p&gt;And the other truth is, agency life (or running any business) can lend itself towards burning out.&lt;/p&gt;
&lt;p&gt;It can feel like an endless marathon, and even if you “make it”, it can feel like best case scenario - you’ll just get more work, more projects, and you’ll just have to work harder.&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t have all the answers, but I have a couple of examples so far in my life.&lt;/p&gt;
&lt;h2 id=&quot;my-first-taste-of-burnout&quot;&gt;My first taste of burnout&lt;/h2&gt;
&lt;p&gt;I have two distinct memories of work-related burnout… so far at least.&lt;/p&gt;
&lt;p&gt;The first time was during a startup I was trying to get off the ground before I started my agency. We’d built the MVP over a year (way too long!), we took part in a startup accelerator and were trying to raise money (way too early!), and not too surprisingly, were struggling to find customers and product market fit.&lt;/p&gt;
&lt;p&gt;One morning I woke up and felt like I’d hit a wall. I had zero enthusiasm for my startup.&lt;/p&gt;
&lt;p&gt;The little things seemed impossible. In fact, I felt like I never wanted to speak to any of my team members again, never wanted to talk about my startup again, and I had lost all faith in my ability to do anything.&lt;/p&gt;
&lt;p&gt;It felt like I almost instantly fell out of love with the things I loved.&lt;/p&gt;
&lt;p&gt;But the truth is, it accumulated over many months. Slowly, and sneakily, my brain and body wearied as I spent thousands of hours trying to get this thing off the ground.&lt;/p&gt;
&lt;p&gt;I thought I had an ok work/life balance because I didn’t sit at my computer all day - but really - all I thought about was my startup, all I talked about was my startup, and all I cared about was my startup.&lt;/p&gt;
&lt;p&gt;When burnout hit, it hit hard, and I didn’t have the skills back then to tackle it, or even realise what it was. So I just quit.&lt;/p&gt;
&lt;p&gt;It took many months to regain my confidence and sense of self. It was only then I started to realise my situation crept up slowly, and most of it was of my own doing.&lt;/p&gt;
&lt;h2 id=&quot;my-second-dance-with-burnout&quot;&gt;My second dance with burnout&lt;/h2&gt;
&lt;p&gt;Fast forward… I’d worked for a few other startups, then gone into freelancing, and finally started my own agency.&lt;/p&gt;
&lt;p&gt;4 years into my agency, we were doing awesomely. We had a team of 13, a fantastic office, and great clients - but something felt… off.&lt;/p&gt;
&lt;p&gt;I recognised the symptoms: being unmotivated with things I’d previously loved, constantly tired and stressed, having (and causing) conflict with my business partners, and where I was normally a confident person - feeling completely out of my depth and overwhelmed.&lt;/p&gt;
&lt;p&gt;The difference was this time the business wasn’t a struggling startup, it was an agency going well. Really well, lots of money, lots of clients, externally this was exactly what I wanted.&lt;/p&gt;
&lt;p&gt;Without having a clear time when it started, you can start to normalise burnout, and question yourself that “maybe I always felt this way?” - but the second time around I knew it wasn’t the case. That’s not the real me, and I need to do something about this.&lt;/p&gt;
&lt;h2 id=&quot;avoiding-burnout&quot;&gt;Avoiding burnout&lt;/h2&gt;
&lt;p&gt;Now, this is the bit that really feels like a self-help article, but I can’t talk about burnout without talking about how to avoid it. I’m certainly no pro - and as with everything on Dev to Agency, this is just my experience, and yours may totally vary.&lt;/p&gt;
&lt;p&gt;First thing, everyone&amp;#39;s different. We all have different triggers, and that means we all have different ways of mitigating burnout. But first things first, you need to do some searching, and figure out how you work.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Know your triggers&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It might be crazy long work weeks, missing out on important events, or not keeping up your general mental hygiene. Triggers for me are starting to ignore physical activity, and drinking too much alcohol as a temporary way to escape from my stress. I know that if I let my health or fitness slide too long it starts to compound my stress levels. I function quite well in a high-stress environment but if I keep that up for many months and it starts to take its toll.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. Put yourself first&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Take time just for yourself, and treat your physical and mental health like it’s the most important investment. Working super long weeks is sometimes necessary, but don’t use it as an excuse to eat like shit, or avoid things that make you feel good about yourself.&lt;/p&gt;
&lt;p&gt;I find it hard to justify “time off”, but I now know it’s key. I take time off for my mental health, and you should too. Maybe that’s sleeping in and starting work a couple of hours late one day, going to watch a movie, or cancelling plans just to read a book and chill.&lt;/p&gt;
&lt;p&gt;I didn’t do these things initially. I liked to work, computers were my hobby, so it was easy to stay in front of a screen and tinker.&lt;/p&gt;
&lt;p&gt;But just like eating healthy - these things don’t always feel good right away. There’s no “I FEEL AMAZING!” moment, it’s just that it can stop you from feeling less amazing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3. Emphasise family and friends&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Talking to people who aren&amp;#39;t in my work bubble is key for me to get out of my own head, and realise there’s a big wide world out there (and everyone has their own problems!).&lt;/p&gt;
&lt;p&gt;There were times when I felt too busy to attend a dinner party or to see a band with mates - but these days I make it one of my highest priorities. Taking those few hours won’t kill your business, in fact, I’m confident that (for me), it cultivates more energy to put towards my business.&lt;/p&gt;
&lt;h2 id=&quot;recovering-from-burnout&quot;&gt;Recovering from burnout&lt;/h2&gt;
&lt;p&gt;With my first taste of burnout, recovery took a while, close to a year. I felt a lot of guilt because I didn’t understand what happened. I lost trust in myself, how can my feelings for something just change so fast? Will this keep happening to me? Why couldn’t I stop it?&lt;/p&gt;
&lt;p&gt;But my second time, I saw it coming before it was too late, and I took some time off with my wife in southeast Asia.  I was still very much in the pre-burnout zone, but that trip gave me time to break the loop of my endless day-to-day thinking and gave me space to think slightly more long-term, and strategically.&lt;/p&gt;
&lt;p&gt;Within the next 6 months, we choose to let around 50% of our clients go, and sadly a few staff members. We needed to operate at a sustainable long-term pace, I didn’t want anyone working more than 38 hours per week - including myself. We put in place strong processes and procedures with our clients to reduce everyone&amp;#39;s stress, and we because a lot better at setting realistic expectations.&lt;/p&gt;
&lt;p&gt;I learnt to delegate. I hired my first senior-level solutions architect, and along with my wife as project manager, they took over one of our largest clients so I could focus on the remaining part of the business.&lt;/p&gt;
&lt;p&gt;I went to the gym religiously right in the middle of the day, even though I rarely wanted to. It was really hard for me mentally to leave work at that time, but afterwards, it made me feel good, feel proud of myself - and for me, feeling like you are accomplishing things is a huge part of recovering.&lt;/p&gt;
&lt;p&gt;I’ll be honest - at that time I was very close to just shutting down my agency. Just like with my original startup, I wanted to completely walk away, and never speak to a client or staff member ever again. But I’m really glad it didn’t happen - because the next 4 years at my agency were even better than the first, and a lot more sustainable and happy.&lt;/p&gt;
&lt;p&gt;Burnout happens, especially in states of prolonged stress or uncertainty. And running your own business is a recipe for this, as it’s easy to put yourself under a lot of pressure.&lt;/p&gt;
&lt;p&gt;This is a big reason why many businesses fail. Not just because they run out of money, but because the owners run out of steam.&lt;/p&gt;
&lt;p&gt;So get in early. Prioritize your health, and carve out time to decompress - however that looks for you. Your business will be better off with long-term sustainability, than constant intensity.&lt;/p&gt;
</content:encoded></item><item><title>Interview with Nat Miletic from Clio Websites</title><link>https://www.devtoagency.com/interview-with-nat-miletic-from-clio-websites/</link><guid isPermaLink="false">63b60872b8ce89000163b441</guid><pubDate>Wed, 01 Feb 2023 22:28:18 GMT</pubDate><description>Nat Miletic is the founder of Clio Websites, a web development agency that's been running for over 15 years.</description><content:encoded>&lt;p&gt;&lt;a href=&quot;https://twitter.com/natmiletic?ref=devtoagency.com&quot;&gt;Nat Miletic&lt;/a&gt; is the founder of &lt;a href=&quot;https://cliowebsites.com/?ref=devtoagency.com&quot;&gt;Clio Websites&lt;/a&gt;, a Calgary-based web development company that&amp;#39;s been operating for over 15 years.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve been Twitter friends with Nat for a long time, and I&amp;#39;ve watched him build a large audience around web development and design, so have been looking forward to hearing the story of his agency.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2023/01/nat-miletic-headshot.png&quot; alt=&quot;Nat Miletic from Clio Websites&quot;&gt;&lt;figcaption&gt;Nat Miletic from Clio Websites&lt;/figcaption&gt;&lt;/figure&gt;
&lt;hr&gt;
&lt;h2 id=&quot;can-you-introduce-yourself-clio-websites-to-the-dev-to-agency-readers&quot;&gt;Can you introduce yourself &amp;amp; Clio Websites to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;Hi, my name is Nat Miletic and I am the owner of Clio Websites.&lt;/p&gt;
&lt;p&gt;I have been in web development since I was a teen in the late 1990s. I am passionate about building cool websites and growing my business.    &lt;/p&gt;
&lt;h2 id=&quot;how-did-clio-websites-start&quot;&gt;How did Clio Websites start?&lt;/h2&gt;
&lt;p&gt;I started Clio back in 2007 as a side project. I was helping friends with a website for their new business. One referral after another, I started to grow the business and expand from there.  &lt;/p&gt;
&lt;h2 id=&quot;do-you-have-a-niche-or-an-ideal-customer-type&quot;&gt;Do you have a niche or an ideal customer type?&lt;/h2&gt;
&lt;p&gt;After many years, I started to target mid-sized businesses instead of taking just anyone as a client.&lt;/p&gt;
&lt;p&gt;When you are starting out, you will take on pretty much any project that comes your way. But when the business grows and you have some steady income, you can start being a bit more selective.&lt;/p&gt;
&lt;p&gt;I am also looking to develop industry-related niche offerings based on the experience I have gained with my existing clients.  &lt;/p&gt;
&lt;h2 id=&quot;how-did-you-find-your-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;How did you find your first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;I started by offering to help my family and friends that had a business or were thinking of starting one.&lt;/p&gt;
&lt;p&gt;The rest of my projects came from referrals. The most important thing, in the beginning, is focusing on getting 2-3 initial clients and asking those clients for referrals and repeat business.  &lt;/p&gt;
&lt;h2 id=&quot;what-challenges-did-you-face-early-on-and-how-did-you-overcome-them&quot;&gt;What challenges did you face early on, and how did you overcome them?&lt;/h2&gt;
&lt;p&gt;The biggest challenge has been keeping up with the latest industry trends, and applying new technology to your offerings.&lt;/p&gt;
&lt;p&gt;As developers and tinkerers, we love to explore and learn new skills. However, not all of them have to be applied to every client project.&lt;/p&gt;
&lt;p&gt;Focusing on a specific skill set and specializing is a much better use of your time than overcomplicating things and always shifting to the latest and greatest.&lt;/p&gt;
&lt;h2 id=&quot;did-you-have-a-clear-vision-of-what-your-business-would-be-when-you-first-started-and-has-that-changed-at-all&quot;&gt;Did you have a clear vision of what your business would be when you first started, and has that changed at all?&lt;/h2&gt;
&lt;p&gt;No not at all. I never thought that I would be specializing in WordPress and marketing.&lt;/p&gt;
&lt;p&gt;I was always a hardcore techy and I loved developing apps, games, and cool websites. Listening to what my clientele needed has made me focus on things that bring us the most revenue, which is WordPress and SEO.  &lt;/p&gt;
&lt;h2 id=&quot;what-challenges-do-you-face-today&quot;&gt;What challenges do you face today?&lt;/h2&gt;
&lt;p&gt;Currently, the biggest challenge is finding and retaining talent.&lt;br&gt;People with these skills are hard to find and there is no shortage of work.&lt;/p&gt;
&lt;h2 id=&quot;what-do-you-think-sets-clio-websites-apart-from-other-agencies&quot;&gt;What do you think sets Clio Websites apart from other agencies?&lt;/h2&gt;
&lt;p&gt;It may sound corny, but we focus on great customer service and delivering on time and on budget.&lt;/p&gt;
&lt;p&gt;We pride ourselves in that and happy customers are way more important to us than profits. This way, we can insure that we are always getting leads, staying busy, and scaling up.  &lt;/p&gt;
&lt;h2 id=&quot;what-do-you-hope-your-business-looks-like-in-3-years&quot;&gt;What do you hope your business looks like in 3 years?&lt;/h2&gt;
&lt;p&gt;We would like to focus on attaining bigger clients that we collaborate with on an ongoing basis and continuing to pump out great looking websites for clients.&lt;/p&gt;
&lt;h2 id=&quot;what-are-3-things-you-would-tell-a-developer-who-is-thinking-of-starting-a-software-agency&quot;&gt;What are 3 things you would tell a developer who is thinking of starting a software agency?&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;You don&amp;#39;t need to be a jack of all trades to open an agency.&lt;/li&gt;
&lt;li&gt;The first few months or years will be hard, but it&amp;#39;s totally worth it and very rewarding.&lt;/li&gt;
&lt;li&gt;You don&amp;#39;t have to know all of the latest technology in order to be successful (pick a tech stack or a tool and master it).&lt;/li&gt;
&lt;/ol&gt;
</content:encoded></item><item><title>Handling toxic clients</title><link>https://www.devtoagency.com/handling-toxic-clients/</link><guid isPermaLink="false">63b606ecb8ce89000163b430</guid><pubDate>Wed, 18 Jan 2023 21:21:38 GMT</pubDate><description>Unfortunately, not all clients are easy to work with. Some may be overly demanding, always negative always blaming you - or even disrespectful or abusive. Often times these are also the clients that are always asking for discounts or penny pinchers - and the ones you have to chase up their invoice payment 5 times before seeing any money. Working with toxic clients can take a toll on your mental health and overall well-being. It’s important to remember that your time and energy are valuable, yo</description><content:encoded>&lt;p&gt;Unfortunately, not all clients are easy to work with. Some may be overly demanding, always negative always blaming you - or even disrespectful or abusive.&lt;/p&gt;
&lt;p&gt;Often times these are also the clients that are always asking for discounts or penny pinchers - and the ones you have to chase up their invoice payment 5 times before seeing any money.&lt;/p&gt;
&lt;p&gt;Working with toxic clients can take a toll on your mental health and overall well-being. It’s important to remember that your time and energy are valuable, your work is valuable - and it’s not worth sacrificing your well-being for a client… especially one that doesn’t appreciate you.&lt;/p&gt;
&lt;h2 id=&quot;the-value-of-a-positive-work-environment-%F0%9F%92%95&quot;&gt;&lt;strong&gt;The value of a positive work environment 💕&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;When I first started my agency, all I cared about was finding work and making enough money for my business to survive. But after we’d built up a regular client base, that fear of “not enough work” started to dissipate - and I could take a breath, and reassess. Had I actually &lt;em&gt;built a company I loved working in?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I mean, I loved most of it. I loved coding, working on cool projects, and hanging out with my team. But, there were a couple of clients who were always negative, they always demanded more, and even though they didn’t spend much money with us, took up a huge amount of time, and expected to get priority treatment over everyone else.&lt;/p&gt;
&lt;p&gt;Relationships like these can bring the energy down, and as a small tight-knit team - our energy and culture were integral.&lt;/p&gt;
&lt;p&gt;As a software development agency, it’s important to create a positive work environment for your team. This includes not only the physical space in which you work, but also the energy and culture of the team. Working with difficult clients can create a negative atmosphere, which can affect the productivity and morale of your team.&lt;/p&gt;
&lt;h2 id=&quot;what%E2%80%99s-their-problem-%F0%9F%A4%94&quot;&gt;What’s their problem? 🤔&lt;/h2&gt;
&lt;p&gt;Just because a client is showing toxic traits this doesn’t mean they are a toxic client, it could mean that your relationship is damaged, but that can be fixed.&lt;/p&gt;
&lt;p&gt;This could be due to many reasons, the way the relationship started, or they may have a problem that they have not communicated, or they may think that&amp;#39;s how they have to deal with businesses to get what they want.&lt;/p&gt;
&lt;p&gt;Whatever it is, there&amp;#39;s really only one way to find out: Communication.&lt;/p&gt;
&lt;p&gt;Arg... hard conversations suck, but they are hard because they are important. They’re hard because they are often things that should have been discussed a lot earlier.&lt;/p&gt;
&lt;p&gt;Have a respectful chat with your client, not via email, but in a meeting (virtual or in person). Certainly don’t call this a “TOXIC CLIENT CHECKUP MEETING” - just a catchup meeting.&lt;/p&gt;
&lt;p&gt;Assuming there is no specific issue, start it off as a general check-in, with questions such as.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How do they feel things have been going?&lt;/li&gt;
&lt;li&gt;Do they feel you are &lt;a href=&quot;https://www.devtoagency.com/how-to-meet-your-clients-expectations/&quot;&gt;meeting their expectations&lt;/a&gt;?&lt;/li&gt;
&lt;li&gt;Have they been happy with the work you are doing?&lt;/li&gt;
&lt;li&gt;Have they had any specific problems?&lt;/li&gt;
&lt;li&gt;What do they think you could improve upon?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These will help tease out some information you may not currently know.&lt;/p&gt;
&lt;p&gt;If you know there’s a specific issue you haven’t talked about, or an issue that comes up in the general discussion, confront it head-on. You need to have this issue resolved, and removed.&lt;/p&gt;
&lt;p&gt;Maintain composure, be polite, be emphatic - but be clear.&lt;/p&gt;
&lt;p&gt;If it’s a problem with the quality of your work, clearly explain the issues. But also mention that software development isn’t like lego - it is significantly more complex. If you feel there were some quality issues that were below standard, own it, and discuss how you will endeavour to stop these issues from taking place in the future.&lt;/p&gt;
&lt;p&gt;If it’s an issue with money - although no one likes talking about money - it has to be done. If they always have a super tight budget, explain to them that they need to allow more padding, because issues will always arise. For example, if they have $10,000 and cannot spend a cent more, then I would recommend we only scope $8000 worth of work, and have a $2k buffer up our sleeve.&lt;/p&gt;
&lt;p&gt;Whatever the problem is, try to calmly, and collaboratively solve it right there on the spot. This cannot happen all the time, but most clients when confronted with a direct conversation will be open to a solution (or at least agree to try a solution).&lt;/p&gt;
&lt;p&gt;Don’t get me wrong, the toxic relationship isn’t all your fault, it might not be your fault at all. However you are in the client services business, and it’s your job to try and build and repair relationships. At least try.&lt;/p&gt;
&lt;h2 id=&quot;what%E2%80%99s-your-problem-%F0%9F%A7%90&quot;&gt;&lt;strong&gt;What’s your problem? 🧐&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Hearing them out is great, but you also need to clearly &lt;a href=&quot;https://www.devtoagency.com/setting-boundaries/&quot;&gt;set or reset your boundaries.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Be clear about what’s not working for you, and how you will need it to work in the future. This may be.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;User acceptance testing is completed within 2 weeks of handing it over&lt;/li&gt;
&lt;li&gt;That all communication is done in a respectful manner&lt;/li&gt;
&lt;li&gt;Invoiced are paid within the agreed timeframe&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.devtoagency.com/managing-scope-creep/&quot;&gt;Uncontrollable scope creep&lt;/a&gt; is having a negative impact on the projects&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Whatever it is. Everyone has different problems - but you need to communicate these unambiguously, and make sure your client understands.&lt;/p&gt;
&lt;p&gt;This may sound like an intense conversation, but it doesn’t need to be as intense as it sounds. Remember, show empathy, be future-focused (don’t bring up past issues, focus on future solutions), and always be respectful.&lt;/p&gt;
&lt;h2 id=&quot;when-it%E2%80%99s-time-to-say-goodbye-detox-time-%F0%9F%91%8B&quot;&gt;&lt;strong&gt;When it’s time to say goodbye (detox time) 👋&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;But after all that sometimes, despite your best efforts, you may find that a client is simply not a good fit for your business. This happens.&lt;/p&gt;
&lt;p&gt;When possible, let them go with grace and poise, and ensure your firing is at the same high standard as your onboarding.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Finish all work to completion (if possible), to the same &lt;a href=&quot;https://www.devtoagency.com/compete-on-quality/&quot;&gt;high quality&lt;/a&gt; you always have.&lt;/li&gt;
&lt;li&gt;Give them advanced notice. You don’t need to be harsh and list the reasons, just tell them you don’t feel this will work out long-term, or your agency is going in a different direction.&lt;/li&gt;
&lt;li&gt;Provide them with a list of alternative agencies or freelancers that could help. Depending on the reasons, you may not want to recommend your friends - however, a quick google search will help you hear. You are in a better position to judge tech companies than they are, so help them out.&lt;/li&gt;
&lt;li&gt;Provide a handover of all source code, documentation, passwords (securely transferred) etc, plus any other information the next agency or freelancer may need - it’s much easier to do this now than in 6 months when a random agency contacts you asking about an API key or something.&lt;/li&gt;
&lt;li&gt;Be sure to officially sign over any &lt;a href=&quot;https://www.devtoagency.com/ownership-of-code-and-intellectual-property/&quot;&gt;code and intellectual property&lt;/a&gt; to them, again, this isn’t something you want to have to deal with in the future.&lt;/li&gt;
&lt;li&gt;Try and end on a high note. Don’t burn bridges unless the bridge is already completely on fire, as you never know what will happen in the future.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;p&gt;It’s ok to let go of clients that are bringing you down. And while it’s important to always be professional and respectful, it’s also important to protect your own well-being and the well-being of your team.&lt;/p&gt;
&lt;p&gt;Setting boundaries, being honest, and prioritising your values are key to maintaining a healthy and successful business.&lt;/p&gt;
&lt;p&gt;Remember, not all clients are for life, and it’s ok to let go of toxic clients (or outgrow clients) just the same as it’s ok for clients to let you go.&lt;/p&gt;
</content:encoded></item><item><title>Setting boundaries</title><link>https://www.devtoagency.com/setting-boundaries/</link><guid isPermaLink="false">63b4c0f3b8ce89000163aff8</guid><pubDate>Wed, 04 Jan 2023 21:32:42 GMT</pubDate><description>Without boundaries, you don’t have a clear cutoff point of what you’re willing to do, and what you’re not willing to do. Whilst this may be ok at the beginning of your business, in the long term knowing exactly where your boundaries are, and communicating these to your clients and staff - will allow you to be more proactive and less reactive. Let’s run through an example without any boundaries set, then the same example of clear boundaries set. Without boundaries 🤷‍♀️ * It’s 7:15 am and you</description><content:encoded>&lt;p&gt;Without boundaries, you don’t have a clear cutoff point of what you’re willing to do, and what you’re not willing to do.&lt;/p&gt;
&lt;p&gt;Whilst this may be ok at the beginning of your business, in the long term knowing exactly where your boundaries are, and communicating these to your clients and staff - will allow you to be more proactive and less reactive.&lt;/p&gt;
&lt;p&gt;Let’s run through an example without any boundaries set, then the same example of clear boundaries set.&lt;/p&gt;
&lt;h2 id=&quot;without-boundaries-%F0%9F%A4%B7%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;Without boundaries 🤷‍♀️&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;It’s 7:15 am and your phone rings just as you get out of the shower, you see it’s a client you worked with mid-last year, so you pick it up.&lt;/li&gt;
&lt;li&gt;Turns out their website’s stopped working for some reason, they are pretty angry as a lot of their business is online.&lt;/li&gt;
&lt;li&gt;You let them know you’ll look into it right away, quickly get dressed, and head over to your computer (a little annoyed, and a little sleepy)&lt;/li&gt;
&lt;li&gt;The client rings you back, just as annoyed - and asks if you have fixed it. You mentioned you have literally just sat down to start looking into it, and you will let them know once it’s fixed.&lt;/li&gt;
&lt;li&gt;It takes you an hour or so to figure out the problem, which turns out to be one of the APIs they use on their homepage has changed overnight, and it’s stopped the site from loading.&lt;/li&gt;
&lt;li&gt;The API provider didn’t announce this change which is frustrating. You find the updated API documentation, and in just over an hour you have fixed the problem.&lt;/li&gt;
&lt;li&gt;You ring your client back and let them know you have fixed the problem. They are still annoyed, but less annoyed.&lt;/li&gt;
&lt;li&gt;You’re happy that the problem’s over as you have a lot of other work to do, finally eat a quick breakfast - and head into your office.&lt;/li&gt;
&lt;li&gt;At the end of the month, you invoice the client for the 2 hours of work.&lt;/li&gt;
&lt;li&gt;They are furious, and ring you instantly, saying how it’s completely unprofessional to deliver a website that breaks and loses them money - and then charge them to fix it. They refuse to pay the bill.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is an extreme example - but it’s also typical of how many client services business function.&lt;/p&gt;
&lt;p&gt;There are no clear boundaries, &lt;a href=&quot;https://www.devtoagency.com/how-to-meet-your-clients-expectations/&quot;&gt;expectations were not correctly set&lt;/a&gt; - and it affects everyone.&lt;/p&gt;
&lt;p&gt;Let’s look at this scenario again, if clear boundaries had been set.&lt;/p&gt;
&lt;h2 id=&quot;with-boundaries-%F0%9F%99%85%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;With boundaries &lt;strong&gt;🙅‍♀️&lt;/strong&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;It’s 7:15 am and your phone rings just as you get out of the shower, you see it’s a client you worked with mid-last year, but you let it go to voicemail. You have no ongoing agreement with this client, and besides - your day doesn’t start until 9 am.&lt;/li&gt;
&lt;li&gt;You have your shower, do a quick meditation, and have some coffee and breakfast.&lt;/li&gt;
&lt;li&gt;You get into the office just before 9 am, check emails, and then check your voicemail from the client. You understand the issue and confirm that their website is actually down.&lt;/li&gt;
&lt;li&gt;Instead of calling the client back, you shoot them a quick email letting them know that you understand the problem, but are very busy at the moment, and as they are not on any support or retainer agreement unfortunately you won’t have time to look into the issue for 2 days. You also remind them (like you have before) of the support plans you offer and attach a PDF outlining the different response and rectification times they get for each plan.&lt;/li&gt;
&lt;li&gt;They reply to the email slightly annoyed - but understanding that as they chose not to go on a support plan previously, the response and rectification times are “as soon as possible”.&lt;/li&gt;
&lt;li&gt;Two days later you look into the problem, see it’s a change in the third-party API that’s in use, and take a quick look at the documentation. You then get back to the client and let them know the problem is not to do with the code you delivered, but that a third party you rely on has changed their API. The fix will be around 2 hours -  and you check if they are happy to pay for this - if so, you can schedule the fix for tomorrow morning, so should be fixed by 10 am.&lt;/li&gt;
&lt;li&gt;They agree, the fix gets done, and they pay their invoice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With the above example, boundaries and expectations had already been set with the client.&lt;/p&gt;
&lt;p&gt;You had previously let the client know about the support plans you offer, and the different response and rectification times they get for the monthly payment.&lt;/p&gt;
&lt;p&gt;They previously understood this, and specifically choose not to go on a support plan - which they then understood meant they get the lowest priority if they have any issues.&lt;/p&gt;
&lt;p&gt;This meant that you didn’t need to answer the call out of hours - in fact, you didn’t have to reply to them until you had the time. This is a boundary that you understood, and they understood - so they could not be surprised when you didn’t pick up the phone.&lt;/p&gt;
&lt;p&gt;The client also understood that after the project is signed off and live - all work is charged for and that there is no free support. This is a boundary you set, and they understood.&lt;/p&gt;
&lt;p&gt;So when it came time to pay for the time spent resolving the issue, there were no questions.&lt;/p&gt;
&lt;h2 id=&quot;what-boundaries-to-set-%F0%9F%9A%AB&quot;&gt;What boundaries to set &lt;strong&gt;🚫&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;You don’t want to be an over-the-top dictator who demands &lt;em&gt;everything&lt;/em&gt; has to be done your way - that’s not the way to &lt;a href=&quot;https://www.devtoagency.com/keeping-your-clients-long-term/&quot;&gt;keep clients long-term&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The boundaries you want to set are the ones that keep you and your team happy, efficient and make for a healthy sustainable work environment.&lt;/p&gt;
&lt;p&gt;For me this meant…&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The working hours for me and my team keep (Mon-Friday, 9-5, not including public holidays or the week between Christmas and New year)&lt;/li&gt;
&lt;li&gt;Unless they are on a high-priority support plan which can include weekends&lt;/li&gt;
&lt;li&gt;The response times for getting back to client requests&lt;/li&gt;
&lt;li&gt;During project delivery - 1 day&lt;/li&gt;
&lt;li&gt;After project sign-off and the project is live - 2 to 3 days, unless on a support plan in which case it depends on their level of support&lt;/li&gt;
&lt;li&gt;Resolution times for dealing with issues reported&lt;/li&gt;
&lt;li&gt;During project delivery - the next sprint&lt;/li&gt;
&lt;li&gt;After project sign-off and the project is live - As soon as possible, but may be up to 2 weeks depending on current projects, unless on a support plan in which case it depends on their level of support&lt;/li&gt;
&lt;li&gt;Costs for dealing with issues&lt;/li&gt;
&lt;li&gt;During project delivery - no cost&lt;/li&gt;
&lt;li&gt;After project sign-off and the project is live - all work is charged at the standard hourly rate&lt;/li&gt;
&lt;li&gt;Issue communication methods&lt;/li&gt;
&lt;li&gt;Email is preferred&lt;/li&gt;
&lt;li&gt;Phone if urgent and on a support plan&lt;/li&gt;
&lt;li&gt;Scoping new work (after the project is live)&lt;/li&gt;
&lt;li&gt;As soon as possible, but may be up to 4 weeks - unless on an ongoing retainer (in which hours can be used for scoping)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Your business may require other boundaries, such as having graphic design files delivered X weeks before development, or never contacting you directly, but instead via your account manager. This is all up to you, and the boundaries you need for your business to thrive.&lt;/p&gt;
&lt;h2 id=&quot;how-to-set-boundaries-%E2%9C%85&quot;&gt;How to set boundaries &lt;strong&gt;✅&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;You don’t do this in a “boundary-setting session” - you do it in an ongoing, consistent manner throughout the life of your relationship.&lt;/p&gt;
&lt;p&gt;It starts with &lt;a href=&quot;https://www.devtoagency.com/how-to-meet-your-clients-expectations/&quot;&gt;setting expectations&lt;/a&gt; up front, letting them know how you work, along with what you are willing to do, and what you’re not willing to do. A &lt;a href=&quot;https://www.notion.so/Setting-boundaries-aac719fc6609421289b7464e20be2bec?ref=devtoagency.com&quot;&gt;project workshop&lt;/a&gt; is a good time to introduce this, but you should also capture this in a signed agreement with your client, as talking is great - but things need to be written down.&lt;/p&gt;
&lt;p&gt;As the project nears delivery you should remind them how you handle &lt;a href=&quot;https://www.devtoagency.com/recurring-revenue/#ongoing-support-%E2%98%8E%EF%B8%8F&quot;&gt;ongoing support and maintenance&lt;/a&gt; - and that if they want priority service they will need to pay monthly for this.&lt;/p&gt;
&lt;p&gt;And lastly, you need to reinforce your boundaries every time they get stretched.&lt;/p&gt;
&lt;p&gt;Whilst it’s ok to break your own rules every once and a while (e.g. doing a small change on the weekend for a very important client) - you need to show your standards and be consistent - so boundary setting is often an ongoing task.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Without setting boundaries, you will always be reactive, acting based on how you feel on the day as opposed to a strategic, consistent method you’ve laid out - and clearly communicating to your clients and staff.&lt;/p&gt;
&lt;p&gt;Build a business you want to work in&lt;/p&gt;
&lt;p&gt;Build a business with boundaries that protect you and your team.&lt;/p&gt;
</content:encoded></item><item><title>Bug free software</title><link>https://www.devtoagency.com/bug-free-software/</link><guid isPermaLink="false">639ba266d888f600014412a5</guid><pubDate>Wed, 21 Dec 2022 21:33:29 GMT</pubDate><description>When it comes to software development, one of the most important goals is to create a product that is bug-free… or at least as bug-free as possible. We all know software bugs can cause a range of issues, from minor annoyances to major disruptions and even security vulnerabilities. Bugs mean more development work and more time re-testing, and if the system is very buggy - it can impact the relationships with your clients. But not every bug is the same. To create software that is as bug-free as</description><content:encoded>&lt;p&gt;When it comes to software development, one of the most important goals is to create a product that is bug-free… or at least as bug-free as possible.&lt;/p&gt;
&lt;p&gt;We all know software bugs can cause a range of issues, from minor annoyances to major disruptions and even security vulnerabilities.&lt;/p&gt;
&lt;p&gt;Bugs mean more development work and more time re-testing, and if the system is very buggy - it can impact the relationships with your clients.&lt;/p&gt;
&lt;p&gt;But not every bug is the same. To create software that is as bug-free as possible, it&amp;#39;s important to first understand where bugs are most likely to occur and how to prevent them.&lt;/p&gt;
&lt;p&gt;There are three main places where bugs can happen in software:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Bugs in requirements&lt;/li&gt;
&lt;li&gt;Bugs in understanding the requirements&lt;/li&gt;
&lt;li&gt;Bugs in code&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Each type of bug arises differently and requires a different method of mitigation.&lt;/p&gt;
&lt;p&gt;Let’s jump into each of these in more detail.&lt;/p&gt;
&lt;h2 id=&quot;bugs-in-your-requirements-%F0%9F%90%9E&quot;&gt;Bugs in your requirements 🐞&lt;/h2&gt;
&lt;p&gt;These are issues that arise when the requirements for a software project are either incorrect or incomplete.&lt;/p&gt;
&lt;p&gt;An example is your client asking for an automated text message to be sent to them when a user upgrades their account, but this feature was either missed or forgotten during the scoping and confirmation phases. So it never became part of the requirements.&lt;/p&gt;
&lt;p&gt;The main reasons requirements bugs arise:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Poor communication between the client and yourself&lt;/li&gt;
&lt;li&gt;Ineffective documentation/requirements-gathering practises&lt;/li&gt;
&lt;li&gt;Ineffective client confirmation/requirements sign-off&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;To avoid requirements bugs, ensure you have great communication from the start.&lt;/p&gt;
&lt;p&gt;Spend a lot of time deeply discussing the problem and the possible solutions (a project workshop is a perfect place for this), and ensure you are documenting all the outcomes.&lt;/p&gt;
&lt;p&gt;I would take a lot of notes, but also do audio recordings of all workshops. The audio is integral as if you are both facilitating the workshop and trying to remember all the discussions and outcomes - this is a monumental task!&lt;/p&gt;
&lt;p&gt;After your requirements gathering sessions, go back over your notes right away and flesh them out whilst the conversations are still clear in your head. If you need to, revisit the audio recordings, and then do another round of fleshing out the notes.&lt;/p&gt;
&lt;p&gt;I would then create user stories, user personas, and user journeys from all this information - and would use a tool such as &lt;a href=&quot;https://userdoc.fyi/?utm_source=newsletter&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=dta&amp;amp;utm_id=dta&quot;&gt;Userdoc&lt;/a&gt; to centralise it all.&lt;/p&gt;
&lt;p&gt;Ask questions right away, confirm everything you need, and then add the answers back into your requirements. The longer you leave this process, the greater chance you miss small details.&lt;/p&gt;
&lt;p&gt;Gathering the requirements is one part, but confirming the requirements is equally important.&lt;/p&gt;
&lt;p&gt;Send your client a copy of the requirements (e.g. invite them to &lt;a href=&quot;https://userdoc.fyi/?utm_source=newsletter&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=dta&amp;amp;utm_id=dta&quot;&gt;Userdoc&lt;/a&gt; - or send them a digital version), as often they might need some time to look through it all and prepare any questions&lt;/p&gt;
&lt;p&gt;Then organise a session with your client where you take them through every requirement one by one, verbally discuss it, and get them to confirm if it seems correct and if anything is missing.&lt;/p&gt;
&lt;p&gt;This may take a couple of hours or more, but in my experience, it’s an integral step in avoiding requirement bugs - and setting up the project with the best chance of success.&lt;/p&gt;
&lt;h2 id=&quot;bugs-in-understanding-%F0%9F%90%9B&quot;&gt;Bugs in understanding 🐛&lt;/h2&gt;
&lt;p&gt;These are issues that arise when the requirements for a software project are correct but are misunderstood during the implementation process.&lt;/p&gt;
&lt;p&gt;An example is a requirement around “Sending notifications on account upgrade” originally being asked to be a text message by your client, but was not communicated correctly to the developers, so they assumed it was an email notification, so implemented it as such.&lt;/p&gt;
&lt;p&gt;If you’re the one implementing the code then this is less likely to occur - as you’ve already gone through the process of avoiding requirements bugs, and you will know the system very well.&lt;/p&gt;
&lt;p&gt;But if others are building or helping build the projects, this increases the chance of bugs around misunderstanding the requirements.&lt;/p&gt;
&lt;p&gt;The main reasons misunderstanding bugs arise:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Poor communication between you and your team&lt;/li&gt;
&lt;li&gt;Unclear or ambiguous task descriptions&lt;/li&gt;
&lt;li&gt;Lack of project management processes&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;To avoid misunderstanding bugs within your team, you need to solid handover process to ensure the project context ends up in your team&amp;#39;s head.&lt;/p&gt;
&lt;p&gt;Developers and designers are not expected to know every single requirement by heart, as they may not work on them all. But it’s still important to take them through the agreed requirements, so they can understand the larger goals, and be aware of what the end result will be.&lt;/p&gt;
&lt;p&gt;If you skip this step and just assign people tasks without educating them on the broader system - then it’s more likely they have misunderstandings.&lt;/p&gt;
&lt;p&gt;When breaking down the implementable project tasks, I recommend you link them back to the source of truth in the project requirements, instead of just re-writing them. These requirements are what the client agreed to, and what they should use for testing, so they should also be what the developers use for implementation. If you store your requirements in a manner where each one has a distinct URL (such as &lt;a href=&quot;https://userdoc.fyi/?utm_source=newsletter&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=dta&amp;amp;utm_id=dta&quot;&gt;Userdoc&lt;/a&gt;, a page in Confluence, or Notion), then your assigned tasks can link directly to the specific page.&lt;/p&gt;
&lt;p&gt;But no matter how hard you try, misunderstandings still occur - and that’s ok.&lt;/p&gt;
&lt;p&gt;The best thing you can do is to catch them early, and a great way (if you&amp;#39;re a programmer) is to always do peer code reviews. Before a task can be deemed “complete”, ensure that the code matches the requirements, as besides educating the coders and giving them detailed requirements, the next line of defence in ensuring they have implemented it as planned is the code itself.&lt;/p&gt;
&lt;h2 id=&quot;bugs-in-your-code-%F0%9F%AA%B2&quot;&gt;Bugs in your code 🪲&lt;/h2&gt;
&lt;p&gt;These are issues that arise when the requirements are correct and understood correctly, but there is an issue with the implementation of the code.&lt;/p&gt;
&lt;p&gt;An example is a requirement around “Sending notifications on account upgrade”. The developer correctly implements the feature to send a text message to the client when a user upgrades their account, however, they make the mistake of also sending a text message on all account status changes, including when the account is downgraded (which was not what the client wanted).&lt;/p&gt;
&lt;p&gt;The main reasons code bugs arise:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Basic coding/logic errors&lt;/li&gt;
&lt;li&gt;Lack of attention to detail&lt;/li&gt;
&lt;li&gt;Lack of personal testing&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;To prevent code bugs, it&amp;#39;s important to have a solid coding process in place, including good personal testing practices, automated testing, peer testing, and peer code reviews.&lt;/p&gt;
&lt;p&gt;Basic coding and logic errors can be caught by code linters, but also doubled checked in your code pipeline - so enforcing a team-wide standard of tooling can catch a lot of these low-hanging bugs.&lt;/p&gt;
&lt;p&gt;I have a high standard when it comes to development bugs. I’m certainly not “bug-free”, but I’ve spent a long time working on my own testing and debugging practices, and I teach my team to apply the same thoroughness.&lt;/p&gt;
&lt;p&gt;Make &lt;a href=&quot;https://www.devtoagency.com/compete-on-quality/&quot;&gt;high-quality code&lt;/a&gt; something your whole team strives for, and importantly, holds each other accountable for.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Preventing bugs in software requires a combination of thorough requirements understanding, clear communication among team members, and a solid coding process.&lt;/p&gt;
&lt;p&gt;By focusing on these areas, software development teams can work towards creating a product that is as bug-free as possible.&lt;/p&gt;
&lt;p&gt;But, having said all that - it&amp;#39;s important to remember that no software is ever completely bug-free, and it&amp;#39;s inevitable that some issues will arise even with the best prevention measures in place.  That&amp;#39;s why it&amp;#39;s important to have a tight process for identifying and fixing bugs as they arise so that any issues can be addressed quickly and efficiently - without wasting too much time, and costing too much money.&lt;/p&gt;
</content:encoded></item><item><title>How to raise your prices</title><link>https://www.devtoagency.com/how-to-raise-your-prices/</link><guid isPermaLink="false">638f04d9d888f60001440e15</guid><pubDate>Wed, 07 Dec 2022 09:31:03 GMT</pubDate><description>As your agency grows, you will want to raise your prices. But make sure you do it the right way.</description><content:encoded>&lt;p&gt;When starting out, it’s hard to know exactly &lt;a href=&quot;https://www.devtoagency.com/how-much-should-you-charge/&quot;&gt;how much to charge&lt;/a&gt;.  And that&amp;#39;s totally fine. You learn more from every project and get better and better.&lt;/p&gt;
&lt;p&gt;But as your business grows, you will often want to &lt;a href=&quot;https://www.devtoagency.com/when-to-raise-your-prices/&quot;&gt;raise your prices&lt;/a&gt;. Knowing how to raise your prices is important, as you want to make sure your clients (or at least the ones you want to keep!), don’t feel like you are taking them for granted.&lt;/p&gt;
&lt;h2 id=&quot;price-increases-and-client-education-%F0%9F%93%96&quot;&gt;Price increases and client education 📖&lt;/h2&gt;
&lt;p&gt;As your client services business grows, your costs will likely change, for example&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Realigning salaries to market rate (you may pay yourself too little at the start)&lt;/li&gt;
&lt;li&gt;Investing more in sales and marketing&lt;/li&gt;
&lt;li&gt;Hiring more staff&lt;/li&gt;
&lt;li&gt;Economic inflation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And specifically as a client services business in the technology industry&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Developers cost more as they move from junior to mid-level, to senior&lt;/li&gt;
&lt;li&gt;Devs in certain technologies demand higher wages as popularity grows (e.g. React)&lt;/li&gt;
&lt;li&gt;Staying up to date with technology can involve more professional development time&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So it should never come as a shock to your clients that you will eventually raise your prices. But if you never mention your prices will change, then your clients won’t think about it.&lt;/p&gt;
&lt;p&gt;Make this clear right from the start.&lt;/p&gt;
&lt;p&gt;Let them know you update your prices yearly, and make this a normal part of the conversation.&lt;/p&gt;
&lt;p&gt;Talking about money can be awkward - but it’s business, and money cannot be ignored.&lt;/p&gt;
&lt;p&gt;If you are doing a &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;fixed-price project&lt;/a&gt;, the pricing will obviously not change.&lt;/p&gt;
&lt;p&gt;However, they need to understand that just because you charge $X per hour on this project - you won’t charge that forever.&lt;/p&gt;
&lt;p&gt;In your proposals, list your pricing as your “current pricing” which reinforces the expectation of future cost changes. Plus it also means a client cannot come back in 6 or 12 months and say “let’s start”, and expect the same pricing that was quoted back then.&lt;/p&gt;
&lt;p&gt;For any ongoing contract you work out with your client, ensure you mention your hourly rate is subject to change over time. Don’t make the mistake of being locked into a specific price for many years (unless this is intentional of course).&lt;/p&gt;
&lt;h2 id=&quot;letting-clients-know-about-a-price-increase-%F0%9F%92%AC&quot;&gt;Letting clients know about a price increase 💬&lt;/h2&gt;
&lt;p&gt;Say your price is going up $15 per hour. For some clients, this might be annoying, but not a showstopper. However, for other clients, this may be a huge problem. Often you don’t know how a client will react until you tell them - so give them an advanced warning&lt;/p&gt;
&lt;p&gt;I would let my clients know 3 months in advance that my agency&amp;#39;s prices were going up, and I would only let active clients know. I wouldn’t bother telling clients I haven’t worked with for 12 months, they can find out when (and if) they need more work.&lt;/p&gt;
&lt;p&gt;Communicate your price change in an email, and include a small description of &lt;em&gt;why&lt;/em&gt; you are increasing your prices.&lt;/p&gt;
&lt;p&gt;Don’t just mention “To keep up with staff salary costs”. Describe the benefit to them, for example, “to keep offering competitive staff salaries, and ensure the high-quality standards you are used to”.&lt;/p&gt;
&lt;p&gt;Don’t expect you can simply raise your prices, earn more money, and everything turns out perfect - you should be prepared that you might lose some clients.&lt;/p&gt;
&lt;h2 id=&quot;raise-prices-but-keep-your-clients-%F0%9F%92%AA&quot;&gt;Raise prices, but keep your clients 💪&lt;/h2&gt;
&lt;p&gt;If you think there are specific clients that may not respond well to your higher pricing, there are a few things you can do to make the transition easier for them.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Offer a gradual price increase&lt;/li&gt;
&lt;li&gt;Offer a reduced rate to go on a monthly retainer&lt;/li&gt;
&lt;li&gt;Grandfather clients on your previous price&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Offering gradual price increases allow you to increase pricing for long-term or loyal clients gradually over a set period of time (e.g. 6 months). For example, if you are raising your prices by $15 dollars per hour, you could offer them a gradual raise of $5 every 2 months, over 6 months.&lt;/p&gt;
&lt;p&gt;This works well with regular ongoing clients who are money conscious, and also encourages them to front-load their work with you, as the more that can get done sooner, the cheaper the rate.&lt;/p&gt;
&lt;p&gt;It’s also a great time to &lt;a href=&quot;https://www.devtoagency.com/recurring-revenue/#retainers-%F0%9F%94%84&quot;&gt;get your clients onto an ongoing retainer&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Having clients on a retainer is gold - I am always happy to give them a small discount if they lock in for 12 months or more.&lt;/p&gt;
&lt;p&gt;Retainers provide better visibility of your future schedule,  guaranteed monthly income, and create more of an ongoing partner relationship over the transaction project-based work.&lt;/p&gt;
&lt;p&gt;It’s also totally fine to “grandfather” client pricing, meaning you keep older clients on older prices, and only raise your prices for new clients.&lt;/p&gt;
&lt;p&gt;When I first started my agency, I hated the idea of clients at different prices.&lt;/p&gt;
&lt;p&gt;It just seemed messy, and I feared it would add a lot of admin overhead.&lt;/p&gt;
&lt;p&gt;Whilst everyone dreams of a productised service business that sells a cookie-cutter solution and basically runs itself, humans are different. Your relationships with these humans are also different, so do what feels right for you.&lt;/p&gt;
</content:encoded></item><item><title>Interview with Cody Benedetto from Modern Launch</title><link>https://www.devtoagency.com/interview-with-cody-benedetto-from-modern-launch/</link><guid isPermaLink="false">6373456b99672a00010358ca</guid><pubDate>Wed, 16 Nov 2022 22:57:08 GMT</pubDate><description>1. Can you introduce yourself &amp; Modern Launch to the Dev to Agency readers? Hello, fellow Dev to Agency readers! My name is Cody Benedetto [https://www.linkedin.com/in/cody-benedetto/]. My co-founder, Ryan Serkes [https://www.linkedin.com/in/ryanserkes/], and I formed Modern Launch [https://modernlaunch.co/] to provide custom software development for startups and high-growth companies. 2. How did Modern Launch start? Ryan and I share a long history of working with technology and custom so</description><content:encoded>&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/11/cody-circle.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;h2 id=&quot;1-can-you-introduce-yourself-modern-launch-to-the-dev-to-agency-readers&quot;&gt;1. Can you introduce yourself &amp;amp; Modern Launch to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;Hello, fellow Dev to Agency readers!&lt;/p&gt;
&lt;p&gt;My name is &lt;a href=&quot;https://www.linkedin.com/in/cody-benedetto/?ref=devtoagency.com&quot;&gt;Cody Benedetto&lt;/a&gt;. My co-founder, &lt;a href=&quot;https://www.linkedin.com/in/ryanserkes/?ref=devtoagency.com&quot;&gt;Ryan Serkes&lt;/a&gt;, and I formed &lt;a href=&quot;https://modernlaunch.co/?ref=devtoagency.com&quot;&gt;Modern Launch&lt;/a&gt; to provide custom software development for startups and high-growth companies.  &lt;/p&gt;
&lt;h2 id=&quot;2-how-did-modern-launch-start&quot;&gt;2. How did Modern Launch start?&lt;/h2&gt;
&lt;p&gt;Ryan and I share a long history of working with technology and custom software. We both have worked directly with and for a wide range of technology companies supporting entrepreneurs, startups, and high-growth companies. In the past decade, we have also launched and sold several companies ranging from cryptocurrency fund management software to real estate analytics. This experience in launching and project managing tech products ultimately led us to look past our business ventures to assist other founders in reaching their goals.  &lt;/p&gt;
&lt;h2 id=&quot;3-do-you-have-a-niche-or-an-ideal-customer-type&quot;&gt;3. Do you have a niche or an ideal customer type?&lt;/h2&gt;
&lt;p&gt;We’ve always been very passionate about startups. We’ve worked with entrepreneurs seeking technical co-founders, startups that need to add to their existing internal dev resources, and companies that are struggling to hire top tech talent internally. We are industry agnostic; however, we have done quite a lot of work in fintech, proptech, and connecting Web2 with Web3 technologies.  &lt;/p&gt;
&lt;h2 id=&quot;4-how-did-you-find-your-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;4. How did you find your first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;Our first clients came from our own personal and professional networks. Upon launching, we made a point to share our company goals with our friends, family, and former colleagues. We published &lt;a href=&quot;https://www.linkedin.com/company/modern-launch/?ref=devtoagency.com&quot;&gt;our linkedin page&lt;/a&gt; and quickly gathered 200+ followers which spurred quite a bit of attention. This actually landed a long-term client relationship with someone I hadn’t spoken to in years right from the start. Leveraging relationships has been our key to success thus far.  &lt;/p&gt;
&lt;h2 id=&quot;5-what-challenges-did-you-face-early-on-and-how-did-you-overcome-them&quot;&gt;5. What challenges did you face early on, and how did you overcome them?&lt;/h2&gt;
&lt;p&gt;We faced many of the same challenges many new business owners face, specifically gaining traction, getting our names out there, and building a strong reputation in the space. We needed to get as many quotes out as possible. We did our best to combat the “new guy” struggle by leveraging our expertise and focusing on building trust first. Although the company was new, we weren’t starting at square one so the most important thing was to build on our portfolio and tackle some small new projects ASAP and build on relationships.&lt;/p&gt;
&lt;p&gt;In our early client engagements, we were transparent with our clients about the company being a new entity to build trust up front. This paid off for the most part but we did lose some projects due to our infancy stage. Within 2 months we had several new clients under our belt and were building out a pipeline of work.  &lt;/p&gt;
&lt;p&gt;The sales process was and will forever be a challenge. Early on, estimating and quoting projects was a bottleneck and we quickly realized that we needed to change our approach. We received some valuable feedback from one of our mentors that continues to pay dividends in time and energy saved. It was simple, “Bring up costs on the first call.” Giving clients a rough estimate range from the get go is the best way to quickly set expectations and uncover barriers without wasting time on follow up emails, meetings, and calls.&lt;/p&gt;
&lt;p&gt;We never want to waste anybody’s time and our time is valuable so being transparent about pricing is critical upfront.&lt;/p&gt;
&lt;h2 id=&quot;6-did-you-have-a-clear-vision-of-what-your-business-would-be-when-you-first-started-and-has-that-changed-at-all&quot;&gt;6. Did you have a clear vision of what your business would be when you first started, and has that changed at all?&lt;/h2&gt;
&lt;p&gt;Yes and no.&lt;/p&gt;
&lt;p&gt;I do think our trajectory goals remain the same for our long-term vision. The types of startups and high growth companies that we’ve worked with are very much in line with the target clients we had originally hoped for. However, the way we’ve approached internal process documentation, sales/marketing &amp;amp; business development, and project management has changed drastically and continues to change.&lt;/p&gt;
&lt;p&gt;We try to run the business with an agile startup mentality despite being a service business which can be easier said than done. We stay nimble and if we’re not iterating and testing new things, we’re doing something wrong. Change is good and we are constantly questioning how we can be doing things better. Our goal is to build our team to be stronger and more highly skilled every quarter. I come from a long line of people and team management so building systems and leveraging diverse skillsets is a big priority.  &lt;/p&gt;
&lt;h2 id=&quot;7-what-challenges-do-you-face-today&quot;&gt;7. What challenges do you face today?&lt;/h2&gt;
&lt;p&gt;Scaling our sales pipeline and adding new project management resources is our major focus right now. In order to take on more clients, you need project/product management resources to support them. In order to afford these critical resources, you need more sales. It’s the classic chicken or the egg dilemma and taking calculated risks is the only way to make progress. Right now, our core focus is sales and marketing while carefully expanding our project management team.&lt;/p&gt;
&lt;p&gt;We’re actively building strategic partnerships with other agencies and complimentary service businesses. We’ve found these mutually beneficial partnerships to be some of the most effective ways to facilitate growth and deliver on client expectations. Referrals and strong business relationships are our number one priority and source of closed leads to date.  &lt;/p&gt;
&lt;h2 id=&quot;8-what-do-you-think-sets-modern-launch-apart-from-other-agencies&quot;&gt;8. What do you think sets Modern Launch apart from other agencies?&lt;/h2&gt;
&lt;p&gt;Although we’re a services business, we take a startup approach to product development for our clients.&lt;/p&gt;
&lt;p&gt;We’re a value first agency that focuses on client vision and success, not just building a product that looks good and works well. Honesty and integrity are critical in business relationships and we often work with teams and stakeholders that are not technical and need real feedback. Every project that we take on starts with truly understanding the company and the future goals. We’ve helped many clients strategize alternative and creative approaches to tackling product development in a way that makes sense for them.&lt;/p&gt;
&lt;p&gt;Oftentimes, we help clients save money, time, and valuable resources by focusing on the things that matter most for the business. There are too many dev shops out there that don’t understand startups and entrepreneurship and will simply build without asking the right questions. That’s just not who we are. There’s a base level of business acumen that needs to come with software development for startups and high-growth companies.    &lt;/p&gt;
&lt;h2 id=&quot;9-what-do-you-hope-your-business-looks-like-in-3-years&quot;&gt;9. What do you hope your business looks like in 3 years?&lt;/h2&gt;
&lt;p&gt;Our goal is to build a mature enough sales pipeline and operational structure to scale our team internally, growing the business tenfold. Ryan and I want Modern Launch to be a company that makes a difference for startups and high-growth companies and builds careers for people who share our mindset.&lt;/p&gt;
&lt;p&gt;We’re both extroverts in the product development space so we obviously crave a community of professionals to help us achieve our goals.&lt;/p&gt;
&lt;p&gt;Technology is our passion and we’re excited to take on new impactful projects with our growing team.&lt;/p&gt;
&lt;h2 id=&quot;10-what-are-3-things-you-would-tell-a-developer-who-is-thinking-of-starting-a-software-agency&quot;&gt;10. What are 3 things you would tell a developer who is thinking of starting a software agency?&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Tell everyone you know what you’re planning to do well before you do it. This helps to create external pressure to help guide you through your timeline and achieve what you set out to do. You don’t want to let yourself and all those people down do you? More importantly, doing this spreads the good word before you officially start. Personal connections are the most important thing to starting a new services business. It’s all about who you know (and who they know).&lt;/li&gt;
&lt;li&gt;Business acumen is critical. Hang out where entrepreneurs and business owners hang out. Learn from people who are better than you and keep these relationships. Know what you don’t know and focus on these gaps as early on as possible. You don’t have to be an expert in everything but you do need to be a jack of all trades in order to run a successful services business, especially at the start.&lt;/li&gt;
&lt;li&gt;Sales, sales, sales. Selling is everything. I’m not talking sleazy car salesman tactics, I’m talking about building real strategic relationships, communication skills, and showcasing your expertise by putting the focus on your clients. Learning how to sell is the single most important skill I think every person in any career should actively work on. Word of mouth and referral business still come from “selling” in one way or another. Demonstrating your value is selling and this is the core to a services business.&lt;/li&gt;
&lt;/ol&gt;
</content:encoded></item><item><title>When to raise your prices?</title><link>https://www.devtoagency.com/when-to-raise-your-prices/</link><guid isPermaLink="false">635cae62378ba30001de67cb</guid><pubDate>Wed, 02 Nov 2022 21:09:24 GMT</pubDate><description>There are many ways your agency can charge. Whether it’s fixed price [https://www.devtoagency.com/pricing-fixed-price/] or time and materials [https://www.devtoagency.com/pricing-time-and-materials/], as your business grows in size or in expertise you will want to raise your prices. But when should you raise them? Raise your prices when you have more work than you need 💪 When your pipeline is consistently full, and you have multiple projects booked into the future, this is generally a sign yo</description><content:encoded>&lt;p&gt;There are many ways your agency can charge. Whether it’s &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;fixed price&lt;/a&gt; or &lt;a href=&quot;https://www.devtoagency.com/pricing-time-and-materials/&quot;&gt;time and materials&lt;/a&gt;, as your business grows in size or in expertise you will want to raise your prices.&lt;/p&gt;
&lt;p&gt;But when should you raise them?&lt;/p&gt;
&lt;h2 id=&quot;raise-your-prices-when-you-have-more-work-than-you-need-%F0%9F%92%AA&quot;&gt;Raise your prices when you have more work than you need 💪&lt;/h2&gt;
&lt;p&gt;When your pipeline is consistently full, and you have multiple projects booked into the future, this is generally a sign you’re onto something good. It’s also a sign that your clients are getting value from you.&lt;/p&gt;
&lt;p&gt;Now you can stay this way and keep booking way into the future. Or maybe even grow the team to deal with work you will inevitably win.&lt;/p&gt;
&lt;p&gt;As you accrue more and more ongoing clients who think you’re awesome, it’s a great time to raise your prices.&lt;/p&gt;
&lt;p&gt;If your goal is to stay small(ish), &lt;a href=&quot;https://www.devtoagency.com/compete-on-quality/&quot;&gt;compete on quality&lt;/a&gt; not price, and &lt;a href=&quot;https://www.devtoagency.com/keeping-your-clients-long-term/&quot;&gt;focus on long-term client relationships&lt;/a&gt; - then raising your prices when your pipeline is full is a great way to do it.&lt;/p&gt;
&lt;h2 id=&quot;raise-your-prices-when-you-want-to-be-exclusive-%F0%9F%92%8E&quot;&gt;Raise your prices when you want to be exclusive 💎&lt;/h2&gt;
&lt;p&gt;Sure, raising your prices may mean you lose a couple of potential clients. But if you have already built up a strong client base and a solid reputation, then your total income will be increasing with this change, so overall it can even out.&lt;/p&gt;
&lt;p&gt;I found that by raising my agency&amp;#39;s prices, we actually attracted a different type of client.&lt;/p&gt;
&lt;p&gt;At $80 an hour, we would attract startups, other agencies (outsourcing overflow work) - really anyone. Back then $80 per hour for software development in Australia was a bargain.&lt;/p&gt;
&lt;p&gt;But 4 years later we had more than doubled our pricing, and we had a whole new type of client. Startups were not so interested, but big businesses were ok with it - and we were better at conveying the value we brought to them.&lt;/p&gt;
&lt;p&gt;Sure, it meant having fewer clients, but the clients we did have, earned us a lot more money. This allowed us to be more exclusive and no longer take jobs that didn’t suit what we wanted.&lt;/p&gt;
&lt;h2 id=&quot;raise-your-prices-every-year-%F0%9F%93%86&quot;&gt;Raise your prices every year 📆&lt;/h2&gt;
&lt;p&gt;As a rule of thumb, I think raising your prices every year is a good place to start.&lt;/p&gt;
&lt;p&gt;Say at a 15% increase per year, if you currently charge $100 per hour, then you would charge $115 next year, and after 5 years you would be $153 per hour.&lt;/p&gt;
&lt;p&gt;Now whether that’s high or low for your services I have no idea - but what I do know is that after 5 years of professional experience, you are worth a lot more than your first year.&lt;/p&gt;
&lt;p&gt;You will hit a ceiling with this method, and as with any price increase you need to understand your competition rates. But it’s a nice simple method to follow.&lt;/p&gt;
&lt;p&gt;In my agency, we raised our rates by around 40% per year initially, which was in line with the larger, more valuable clients we were attracting. After 7 years or so, the price didn’t increase so rapidly as we got closer to the top of the market rate for agencies.&lt;/p&gt;
&lt;h2 id=&quot;raise-your-prices-when-your-business-changes-%F0%9F%9A%80&quot;&gt;Raise your prices when your business changes 🚀&lt;/h2&gt;
&lt;p&gt;When you first start out you can be super lean - but as you grow, more costs sneak in.&lt;/p&gt;
&lt;p&gt;More monthly SaaS costs, increased costs for staff or freelancers, plus equipment and training costs. All of this contributes to building a better, more sustainable company, and because your clients directly benefit from this it’s not unreasonable that their costs increase as well.&lt;/p&gt;
&lt;p&gt;But you can also raise your rates along with strategic business decisions.&lt;/p&gt;
&lt;p&gt;For example if my agency wasn’t acquired, then a future direction I would have taken was a 4-day work week for the whole business - but kept everyone on the same salary.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve always loved the idea of this, but it’s a 20% decrease in profit for the whole business. So in return I would have raised our rates to balance this out. Again, we may have lost some clients with this change, but I believe you owe it to yourself to build the business (and life) that you want.&lt;/p&gt;
&lt;h2 id=&quot;but-not-all-clients-need-to-be-on-the-same-rate-%F0%9F%92%B5&quot;&gt;But not all clients need to be on the same rate 💵&lt;/h2&gt;
&lt;p&gt;There are many reasons you may charge some clients more than others.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Friends, or long-term valued clients&lt;/li&gt;
&lt;li&gt;A startup, that simply cannot afford your new rates&lt;/li&gt;
&lt;li&gt;A “for purpose” or charity organisation&lt;/li&gt;
&lt;li&gt;A strategic alignment or partnership&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Although I often did blanket price increases in my agency, I also left some long-term clients on the previous rate for a few years.&lt;/p&gt;
&lt;p&gt;Whilst I initially didn’t like having clients on different rates (it just seemed “messy”), I learned to realise it’s completely fine, and often how business is done.&lt;/p&gt;
&lt;p&gt;It’s not all about money.&lt;/p&gt;
&lt;p&gt;Now that’s a lot easier to say when you’re making money. But when your costs are covered, and you’re making a good profit, then the long-term value is often more important than short-term value.&lt;/p&gt;
&lt;p&gt;I had startup clients for many years, and they paid around 25% less per hour than my larger clients. It wasn’t too hard to manage, everyone got value, and they appreciated the discount - which in turn built a stronger relationship.&lt;/p&gt;
</content:encoded></item><item><title>How much should you charge?</title><link>https://www.devtoagency.com/how-much-should-you-charge/</link><guid isPermaLink="false">634dde50378ba30001de63b5</guid><pubDate>Wed, 19 Oct 2022 21:02:33 GMT</pubDate><description>We all know money makes the world go around, but knowing how much to charge is one of the harder things to figure out when you start an agency or freelance business. There are many methods (including just guessing), but after years of running my agency I’ve come up with a formula that works well. 1. How much does it cost to run your business? 📈 Tech businesses can have very low overheads in comparison to others, but it’s still important to know your running costs and to recalculate these ever</description><content:encoded>&lt;p&gt;We all know money makes the world go around, but knowing how much to charge is one of the harder things to figure out when you start an agency or freelance business.&lt;/p&gt;
&lt;p&gt;There are many methods (including just guessing), but after years of running my agency I’ve come up with a formula that works well.&lt;/p&gt;
&lt;h2 id=&quot;1-how-much-does-it-cost-to-run-your-business-%F0%9F%93%88&quot;&gt;1. How much does it cost to run your business? 📈&lt;/h2&gt;
&lt;p&gt;Tech businesses can have very low overheads in comparison to others, but it’s still important to know your running costs and to recalculate these every year or so.&lt;/p&gt;
&lt;p&gt;For the sake of this exercise ignore salaries. Meaning don’t take into account what you pay yourself or your staff, as we’ll do that later.&lt;/p&gt;
&lt;p&gt;I recommend creating a spreadsheet and adding every yearly expense - including items like new laptops and other once-off yearly expenses.&lt;/p&gt;
&lt;p&gt;Here are some example costs you need to take into account.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Rent (if applicable, or a portion of your home costs)&lt;/li&gt;
&lt;li&gt;Office costs (water, electricity, gas etc, or a portion of your home costs)&lt;/li&gt;
&lt;li&gt;Phone and internet costs (even if you’re working from home)&lt;/li&gt;
&lt;li&gt;Equipment (laptops, hardware etc, yearly average)&lt;/li&gt;
&lt;li&gt;Supplies (pens, paper, binders, floppy disks!)&lt;/li&gt;
&lt;li&gt;Accountant (tax preparation etc, yearly average)&lt;/li&gt;
&lt;li&gt;Insurance (professional liability insurance etc)&lt;/li&gt;
&lt;li&gt;Legal (contract preparation, reviewing etc)&lt;/li&gt;
&lt;li&gt;Professional development (mentors, coaches, courses, books etc)&lt;/li&gt;
&lt;li&gt;SaaS products (GSuite, HubSpot, LastPass etc.)&lt;/li&gt;
&lt;li&gt;Hosting costs (for your website if applicable)&lt;/li&gt;
&lt;li&gt;Advertising costs (Digital ads, physical ads, subscription services etc)&lt;/li&gt;
&lt;li&gt;Travel costs (for client meetings)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s handy to know your yearly forecasted running costs and your monthly forecasted running costs, as this helps you determine what you need to charge (at minimum) to cover your running costs.&lt;/p&gt;
&lt;p&gt;With my agency, I kept a “current” and “expected” spreadsheet, as data changes year-by-year, and I know with my agency we were generally looking to hire, move office, or raise salaries. So knowing our current expenses and our forecasted future expenses helped us make financial decisions.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;As an example, a small agency may have business running costs (without salaries) of $15,000 per year.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;2-how-much-do-you-need-to-pay-people-%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB&quot;&gt;2. How much do you need to pay people 👩‍💻&lt;/h2&gt;
&lt;p&gt;This includes salaries and expenses to yourself, any full-time staff, and other staff (contractors and freelancers) that regularly help you deliver projects.&lt;/p&gt;
&lt;p&gt;If on occasion you hire contractors to help you deliver specific projects, and you are confident that next year you will hire them for a minimum of X months - then include them in this cost. However, if you’re unsure then simply exclude them, and take their expenses into account on a per-project level (what you charge for each individual project) and not at a general hourly rate level.&lt;/p&gt;
&lt;p&gt;Often new founders pay themselves “whatever is left over” which is fine. However, for the sake of this exercise, I encourage you to actively decide how much you want to earn per year, as that will help you determine what you need to get there.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;As an example, a small agency with one owner and two full-time employees may pay $240,000 in salaries.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;3-how-much-do-you-work-per-week-%E2%8F%B3&quot;&gt;3. How much do you work per week? ⏳&lt;/h2&gt;
&lt;p&gt;This may seem like a silly question as everyone assume work is “5 days per week”, but more and more you see companies working 4 days per week or even a 9-day fortnight.&lt;/p&gt;
&lt;p&gt;On top of this, the founders of new companies may be willing to work more to get things off the ground. So working 50 or even 60 hours per week is not unheard of (just try not to do it for very long!).&lt;/p&gt;
&lt;p&gt;But it’s not just about how much you want to work, you also want to take into account public holidays, personal holidays, sick leave etc - and these figures differ depending on where you live.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;But as an example,  let’s say a small U.S based agency&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Works an average of 35 hours per week per employee&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;W&lt;strong&gt;orks an average of 47 weeks per year per employee&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;4-how-much-downtime-do-you-have-%F0%9F%A4%B7%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;4. How much downtime do you have? 🤷‍♂️&lt;/h2&gt;
&lt;p&gt;Client service work can be &lt;em&gt;famine and feast, and&lt;/em&gt; depending on your specific business you may have two months working at 60% capacity. Then three months of working at &amp;gt; 100%  to deliver a large project on time.&lt;/p&gt;
&lt;p&gt;Your goal is to get paid for that downtime - as that’s part of the game.&lt;/p&gt;
&lt;p&gt;Aim for your &lt;em&gt;famine&lt;/em&gt; times (when work is lean) to be covered by your &lt;em&gt;feast&lt;/em&gt; times (when it’s in abundance), so it all evens out.&lt;/p&gt;
&lt;p&gt;Having clients on ongoing retainers can really help with this calculation, as it makes everything more reliable if they lock in X amount of hours per week or per month.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;As an example, a small agency in their first couple of years of starting may have an estimated downtime of 15% per year across all staff.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This means of the 47 weeks each employee works on average per year, they have 7 weeks of non-billable hours, or downtime when they are not actively on a project.&lt;/p&gt;
&lt;h2 id=&quot;so-where-do-our-calculations-get-us-%F0%9F%A7%AE&quot;&gt;So where do our calculations get us? 🧮&lt;/h2&gt;
&lt;p&gt;Let’s recap on the example company I’ve mentioned so far.&lt;/p&gt;
&lt;p&gt;This small U.S based agency has...&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;An annual business cost of $15,000, and an annual people cost of $240,000&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;So $250,000 - this is the figure we know that agency needs just to keep their business running and for everyone to get paid.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3 staff, who work 35 hours per week, 47 weeks of the year&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;So each staff member works around 1,645 hours per year or 4,935 hours across all 3 team members.&lt;/p&gt;
&lt;p&gt;But remember we estimated &lt;strong&gt;a 15% downtime&lt;/strong&gt; - meaning there is 15% of the hours in the year where the team is not doing billable hours. We need to factor this in, which comes to 4,194.75 hours per year across the team.&lt;/p&gt;
&lt;p&gt;So the yearly costs of $250,000 divided by 4,194.75 (the yearly estimated hours taking into account 15% downtime) come to $59.59.&lt;/p&gt;
&lt;p&gt;Meaning $60 per hour is the minimum hourly rate needed to cover costs, even taking downtime into account.&lt;/p&gt;
&lt;h2 id=&quot;5-awesome-so-how-much-profit-do-you-want-%F0%9F%A4%91&quot;&gt;5. Awesome, so how much profit do you want? 🤑&lt;/h2&gt;
&lt;p&gt;In our example above, anything charged on top of that base $60 per hour will be profit for the business.&lt;/p&gt;
&lt;p&gt;In general, a good profit margin for an agency is between 15% to 20%, but even as high as 30% plus.&lt;/p&gt;
&lt;p&gt;So if $60 per hour is the break-even, then&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;$69 per hour would see a 15% profit&lt;/li&gt;
&lt;li&gt;$72 per hour, 20% profit&lt;/li&gt;
&lt;li&gt;$78 per hour, 30% profit&lt;/li&gt;
&lt;li&gt;And so on…&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Profit for your business isn’t all about swimming in a pool full of cash and buying fur coats, it’s about being strategic.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Building up an emergency fund to handle any unexpected events (I recommend 3 months worth of business and salary costs saved up)&lt;/li&gt;
&lt;li&gt;Putting the profit back into the business to hire or staff, advertise more, or acquire other assets (like other businesses).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At the start of your agency, your profit margins will most likely be lower. But as you get more experienced, and build a larger network of clients - your profit margin can shoot up fast.&lt;/p&gt;
&lt;h2 id=&quot;6-but-how-much-do-your-competitors-charge-%F0%9F%A4%BC%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;6. But how much do your competitors charge? 🤼‍♀️&lt;/h2&gt;
&lt;p&gt;It’s all very well working out how much you &lt;em&gt;want&lt;/em&gt; to charge - but that doesn’t mean it’s how much you &lt;em&gt;can&lt;/em&gt; charge.&lt;/p&gt;
&lt;p&gt;The market will tell you if your rates are too high, as clients will go with your competitors. That is unless you offer awesome service that’s worth the price.&lt;/p&gt;
&lt;p&gt;When working out your hourly rate, identity your competitors, and find out how much they charge. This is might be as simple as checking out their website, or looking them up on &lt;a href=&quot;http://clutch.co/?ref=devtoagency.com&quot;&gt;clutch.co&lt;/a&gt;. You might need to do some sneaky research. But generally hourly rates are not a secret, as my agency would be transparent about our rates in our first chat with a potential client.&lt;/p&gt;
&lt;p&gt;If your rate is significantly higher than your competitors, you might want to either.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Work on your value offering, so you really stand out - and make it clear to clients what they are getting for their extra dollars&lt;/li&gt;
&lt;li&gt;Reduce your rates&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I would always recommend #1, but sometimes you may need to also reduce your rates whilst you figure this out.&lt;/p&gt;
&lt;h2 id=&quot;7-how-badly-do-you-want-the-project-%F0%9F%A4%9E&quot;&gt;7. How badly do you want the project? 🤞&lt;/h2&gt;
&lt;p&gt;Working out your minimum hourly rate is important. It helps you know your base costs and allows you to make informed decisions.&lt;/p&gt;
&lt;p&gt;But an informed decision might mean not making much profit on a project because you see the business profiting - even if not a huge financial profit.&lt;/p&gt;
&lt;p&gt;An example is one of the first large projects my agency took on. It was by far the biggest project we had won, but we knew we would only win it if we make less profit than normal (maybe close to 10%).&lt;/p&gt;
&lt;p&gt;But for me, it was the right decision, as this client brought a lot more work in the future, and it was a high-profile project that was a great case study for attracting future clients.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Money can be a very emotional thing.&lt;/p&gt;
&lt;p&gt;But by clearly calculating your minimum “break-even” costs, you can approach your rates more strategically.&lt;/p&gt;
&lt;p&gt;You still need to accurately &lt;a href=&quot;https://www.devtoagency.com/managing-scope-creep/&quot;&gt;manage scope creep&lt;/a&gt; and choose the right &lt;a href=&quot;https://www.devtoagency.com/pricing-hybrid/&quot;&gt;pricing method&lt;/a&gt; that works for you. But knowing how much your business needs to cover the basics, and make a profit - that’s the first step.&lt;/p&gt;
</content:encoded></item><item><title>How to balance technical debt</title><link>https://www.devtoagency.com/balancing-technical-debt/</link><guid isPermaLink="false">633d2642378ba30001de5fbe</guid><pubDate>Wed, 05 Oct 2022 08:37:21 GMT</pubDate><description>I’ve been a programmer for most of my life, between working for enterprise companies, and startups, and then running my own software development company, so I have seen the impacts of technical debt from all angles. Avoiding tech debt isn’t as simple as saying “don’t do it”. I would say every single software project has a technical debt of some kind (and not all are accidental). I think the best you can do is understand and be aware of it. What is technical debt? 💸 Technical debt is the futu</description><content:encoded>&lt;p&gt;I’ve been a programmer for most of my life, between working for enterprise companies, and startups, and then running my own software development company, so I have seen the impacts of technical debt from all angles.&lt;/p&gt;
&lt;p&gt;Avoiding tech debt isn’t as simple as saying “don’t do it”. I would say every single software project has a technical debt of some kind (and not all are accidental).&lt;/p&gt;
&lt;p&gt;I think the best you can do is understand and be aware of it.&lt;/p&gt;
&lt;h2 id=&quot;what-is-technical-debt-%F0%9F%92%B8&quot;&gt;What is technical debt? 💸&lt;/h2&gt;
&lt;p&gt;Technical debt is the future cost you take on by doing things quickly, and then having to pay for it later on.&lt;/p&gt;
&lt;p&gt;Some examples include.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Poor code quality&lt;/li&gt;
&lt;li&gt;Rushed architecture decisions&lt;/li&gt;
&lt;li&gt;Using low-quality or unmaintained libraries&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And like financial debt, tech debt will (most likely) need to be paid back.&lt;/p&gt;
&lt;h2 id=&quot;what%E2%80%99s-the-problem-with-technical-debt-%F0%9F%98%AC&quot;&gt;What’s the problem with technical debt? 😬&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;You cannot spend your way out of recession or borrow your way out of debt&lt;/em&gt;”&lt;br&gt;- Daniel Hannan, Writer and politician&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Let’s say we are building a new web application for a client, allowing musicians from around the world to jam in real-time together.&lt;/p&gt;
&lt;p&gt;We go through a scoping phase, and a UI design phase and the client gives the “all clear” to start building.&lt;/p&gt;
&lt;p&gt;Awesome, I’m excited!&lt;/p&gt;
&lt;p&gt;But when designing and building software, hundreds of decisions need to get made.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What backend framework should we use?&lt;/li&gt;
&lt;li&gt;What database?&lt;/li&gt;
&lt;li&gt;What frontend tech?&lt;/li&gt;
&lt;li&gt;How should we stream the audio? WebSockets, WebRTC, HTTP Live Streaming?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each of these decisions takes you down a road. And each road has its own little twists and turns.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ok, let’s go with React, good choice&lt;/li&gt;
&lt;li&gt;Should we use a state management library like Redux?&lt;/li&gt;
&lt;li&gt;Do we leverage a UI library?&lt;/li&gt;
&lt;li&gt;Which one? Material UI? Ant Design? Semantic?&lt;/li&gt;
&lt;li&gt;Should we automate front-end testing?&lt;/li&gt;
&lt;li&gt;Using Jest? Mocha? Cypress?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These decisions themselves aren’t technical debt, but they do have the potential to cause or increase technical debt.&lt;/p&gt;
&lt;p&gt;For the real-time music jamming web app, you decide to use a specific React UI library you have used before, that previously made things run a lot faster. This project has a really specific UI design and is quite groundbreaking in fact.&lt;/p&gt;
&lt;p&gt;As the project gets underway you realise that whilst simple UI components are a lot faster to create, more complex UI actually takes longer, as you have to customise the library to match the approved design.&lt;/p&gt;
&lt;p&gt;Building on top of the existing UI library still saved time - just not as much as you had hoped.&lt;/p&gt;
&lt;p&gt;This decision doesn’t just affect this specific delivery, it will affect every piece of UI work on this project in the future too. Whether it’s you working on it, or someone else.&lt;/p&gt;
&lt;p&gt;This is where technical debt slips in.&lt;/p&gt;
&lt;p&gt;A decision to get today&amp;#39;s work done faster can often affect tomorrow&amp;#39;s work.&lt;/p&gt;
&lt;h2 id=&quot;is-all-tech-debt-bad-%F0%9F%91%8E&quot;&gt;Is all tech debt bad? 👎&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;It’s not that paying down technical debt will make your startup successful. It’s that successful startups have the luxury of paying down technical debt&lt;/em&gt;”&lt;br&gt;- Naval Ravikant, Entrepreneur and investor&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Importantly there are 2 types of technical debt.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Accidental tech debt&lt;/strong&gt; - where you make a decision you don’t realise will hold the system back in the future&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deliberate tech debt&lt;/strong&gt; - where you make a decision you know may hold the system back in the future, but right now it is the best decision&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Avoiding accidental tech debt comes with experience, but there are strategies you can employ to mitigate the chances of it occurring.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Measure twice, cut once (spend more time planning and researching, before jumping into coding)&lt;/li&gt;
&lt;li&gt;Research all libraries and frameworks deeply before use&lt;/li&gt;
&lt;li&gt;Employ best practice code standards such as linting, peer review, and automated testing&lt;/li&gt;
&lt;li&gt;Refactor fast, as soon as you notice any sign of a possible technical debt&lt;/li&gt;
&lt;li&gt;Book in dedicated time for maintenance and refactoring&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Deliberate tech debt is a whole other thing.&lt;/p&gt;
&lt;p&gt;In my previous example about the collaborative music jamming app, I would say that the decision about saving some time by using the UI library comes down to the delicate balance of what&amp;#39;s most important.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Time&lt;/li&gt;
&lt;li&gt;Cost&lt;/li&gt;
&lt;li&gt;Quality&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If time is most important, then go with whatever gets the first version of the project done as fast as possible -  even if that means future work may be a bit slower.&lt;/p&gt;
&lt;p&gt;If cost is the highest priority, then look for the cheapest way to get done.&lt;/p&gt;
&lt;p&gt;If it’s quality, you need to build in the best way you can (and perhaps that involves having complete control over the UI and not building on a framework that might restrict you in the future.&lt;/p&gt;
&lt;h2 id=&quot;it%E2%80%99s-not-all-on-your-shoulders-%F0%9F%A4%9D&quot;&gt;It’s not all on your shoulders 🤝&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;The risk of a wrong decision is preferable to the terror of indecision&lt;/em&gt;”&lt;br&gt;- Maimonides, Philosopher&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Your client doesn’t know about databases, WebSockets, or React UI libraries - that’s your department.&lt;/p&gt;
&lt;p&gt;But your client does know what&amp;#39;s most important to them and their project, so the decision of time vs cost vs quality is really a decision for them, not you.&lt;/p&gt;
&lt;p&gt;In a &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;project scoping workshop&lt;/a&gt; or a discovery session I specifically ask the client to pick what are the main priorities of the project, and the tradeoffs they are willing to live with.&lt;/p&gt;
&lt;p&gt;They can pick two of the following (but not all three).&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Time&lt;/li&gt;
&lt;li&gt;Cost&lt;/li&gt;
&lt;li&gt;Quality&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I explain why all three aren’t realistic (at least for most budgets), and clients understand this once you explain that software development isn’t just a science, it’s also an art.&lt;/p&gt;
&lt;p&gt;Based on the two priorities they choose, you can then make the smartest decision you can in regards to balancing technical debt, and balancing what the client sees as the highest priorities.&lt;/p&gt;
&lt;p&gt;For example, a startup might be looking to get an MVP built, in which case they would most likely choose time and cost as their highest priorities.&lt;/p&gt;
&lt;p&gt;In this case, I would make technical decisions that may not be the highest for long-term quality, but prioritise saving money, and getting to market quicker.&lt;/p&gt;
&lt;p&gt;Or another example is a large enterprise organisation may choose time and quality as their highest priorities.  Then I would add more developers to the project to try and get it done faster (although we all know doubling the devs doesn’t halve the time!). I would also put significant effort into making sure the system is developed to the highest quality standards.&lt;/p&gt;
&lt;p&gt;I recommend being open and telling clients about any large technical trade-offs you recommend implementing.&lt;/p&gt;
&lt;p&gt;For example, my agency once built a mobile application using Parse, a Platform-as-a-Service SaaS that allowed us to get things done really fast. I suggested this to the client and outlined the pros and cons of using a PaaS over building it from scratch, and we both agreed that for the startup it was best suited.&lt;/p&gt;
&lt;p&gt;Facebook then acquired Parse shortly after, and about 12 months later Parse shut down its SaaS, and we had a few months to move platforms.&lt;/p&gt;
&lt;p&gt;This sucked, but sh*t happens. Especially when you are relying on other services or libraries.&lt;/p&gt;
&lt;p&gt;Even though it wasn’t a perfect situation, I was glad I involved my client in the original decision to use a PaaS, as they got to make an informed decision about the trade-offs involved.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Like most things, the more you practise the better you will get.&lt;/p&gt;
&lt;p&gt;Identifying accidental technical debt is definitely one of those things, and this was a big role I played in my agency, and is a core responsibility of any technical lead or CTO.&lt;/p&gt;
&lt;p&gt;Helping balance deliberate technical debt is often a little harder to learn, as just like balancing debt on a credit card, it can get out of control quite easily.&lt;/p&gt;
&lt;p&gt;Just remember to involve your client in these conversations, as success is collaborative.&lt;/p&gt;
</content:encoded></item><item><title>5 common estimation mistakes</title><link>https://www.devtoagency.com/5-common-estimation-mistakes/</link><guid isPermaLink="false">63313f2138a9cb0001238503</guid><pubDate>Mon, 26 Sep 2022 06:37:28 GMT</pubDate><description>Great client relationships are built upon meeting (and hopefully exceeding) expectations, but that can be hard to achieve when your project estimation doesn’t go according to plan. Estimation is hard, and I’m not the first to say that. It can take many years and a lot of experience for someone to become a great estimator, but you don’t always have that luxury when starting your own agency or freelance business. You need to provide estimates now, and need to do them as best you can. I’ve been</description><content:encoded>&lt;p&gt;Great client relationships are built upon meeting (and hopefully exceeding) expectations, but that can be hard to achieve when your project estimation doesn’t go according to plan.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Estimation is hard, and I’m not the first to say that.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It can take many years and a lot of experience for someone to become a great estimator, but you don’t always have that luxury when starting your own agency or freelance business. You need to provide estimates now, and need to do them as best you can.&lt;/p&gt;
&lt;p&gt;I’ve been writing software estimates for nearly 20 years, and below are 5 common mistakes and remedies I’ve integrated to improve my estimation.&lt;/p&gt;
&lt;h2 id=&quot;1-bad-requirements-%F0%9F%93%83&quot;&gt;1. Bad requirements 📃&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;I try to prepare for everything beyond the extent of preparation&lt;/em&gt;”&lt;br&gt;- Taylor Swift&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I think this is the primary issue with estimating. Requirements are missed or unclear, and you simply can’t take into account what you don’t know.&lt;/p&gt;
&lt;p&gt;As the saying goes “assumptions are the mother of all f*ckups” - meaning the worse your requirements are, the more assumptions you’re making, and the more risk you’re introducing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To fix this&lt;/strong&gt;: spend more time working with your client to lock down the requirements. Together, create precise acceptance criteria for each task, and make sure everyone is on the same page about exactly what’s required for each feature.&lt;/p&gt;
&lt;p&gt;A &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;Project workshop&lt;/a&gt; is a great time for this, and I use &lt;a href=&quot;https://www.devtoagency.com/living-user-story-documentation/&quot;&gt;User story documentation&lt;/a&gt; to capture the requirements, and then use and build upon them throughout the entire project lifecycle.&lt;/p&gt;
&lt;h2 id=&quot;2-always-thinking-best-case-%F0%9F%A4%9E&quot;&gt;2. Always thinking best-case 🤞&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;The pessimist complains about the wind, the optimist expects it to change, the realist adjusts the sails.&lt;/em&gt;”&lt;br&gt;- William Arthur Ward, Writer&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Most people are overly optimistic, and this has a huge impact on estimations. We trust our gut and generally think of just the “happy path” scenario.&lt;/p&gt;
&lt;p&gt;But as developers, we are also often asked to estimate completely new concepts or technologies - meaning it’s difficult to consider all the unknowns and hidden risks. This is where it pays to have a healthy dose of pessimism.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To fix this&lt;/strong&gt;: don’t just estimate based on your gut feeling, but separately estimate the best case (optimistic), worst case (pessimistic), and most likely case scenarios.&lt;/p&gt;
&lt;p&gt;When doing a “worse case” I find it handy to think very hard about what &lt;em&gt;could&lt;/em&gt; go wrong - as once in a while, these things do go wrong.&lt;/p&gt;
&lt;p&gt;I use the &lt;a href=&quot;https://project-management.info/three-point-estimating-pert/?ref=devtoagency.com&quot;&gt;PERT 3-point estimation&lt;/a&gt; technique, which calculates an expected amount of time or cost based on these three inputs.&lt;/p&gt;
&lt;h2 id=&quot;3-forgetting-the-small-things-%F0%9F%A4%8F&quot;&gt;3. Forgetting the small things 🤏&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“In this bright future, you can&amp;#39;t forget your past.”&lt;br&gt;- Bob Marley&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It’s not uncommon to forget about all the small things involved in the project, but these things add up, and can ultimately have a large effect on the estimate.&lt;/p&gt;
&lt;p&gt;These are often very project or industry-specific, but an example of un-estimated tasks include.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Daily communication&lt;/li&gt;
&lt;li&gt;Weekly 20-minute status meetings&lt;/li&gt;
&lt;li&gt;Time spent talking with other stakeholders (designers)&lt;/li&gt;
&lt;li&gt;Responsive UI testing on different devices&lt;/li&gt;
&lt;li&gt;Setting up and configuring your project tools (project management, source control, continuous integration etc)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It might sound silly at first estimating for “daily communication”, and you might not want to publically call it that to your client (call it “Account management”). However, just 15 minutes a day of emails or Slack messages add up to 10 hours over a 2-month project.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To fix this&lt;/strong&gt;: Have a standard estimate template where you capture all your common line items, then add to the template as you experience new things you want to account for. Over time your estimation template will become a real asset.&lt;/p&gt;
&lt;h2 id=&quot;4-you-are-biased-%F0%9F%98%AC&quot;&gt;4. You are biased 😬&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;All of us show bias when it comes to what information we take in. We typically focus on anything that agrees with the outcome we want&lt;/em&gt;”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;- Noreena Hertz, Academic &amp;amp; economist.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Even if you have collected amazing requirements, and have conducted a thorough best case/worst case estimate, our own opinions are still biased.&lt;/p&gt;
&lt;p&gt;All humans are biased. We only know what we know, and we draw on our past experiences when thinking of the future. This can mean missing concepts due to our blind spots, or always thinking some task is a lot simpler than it is.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To fix this:&lt;/strong&gt; Get another pair of eyes on your estimate, especially really important estimates.&lt;/p&gt;
&lt;p&gt;In my agency, I would have 2 developers and myself do independent estimates, and then we would get together and discuss our results. This would often lead to a combined estimate that was more accurate, as different people bring different perspectives, and help smooth out the biases that any one individual brings.&lt;/p&gt;
&lt;h2 id=&quot;5-not-adding-contingencies-%F0%9F%93%8F&quot;&gt;5. Not adding contingencies 📏&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;When things go wrong, don&amp;#39;t go with them&lt;/em&gt;”&lt;br&gt;- Elvis Presley&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Estimation is black art, and no matter how well you do, sometimes it doesn&amp;#39;t go according to plan. An API you’re integrating with might not work how you expected, or it might change during development. The client might provide &lt;em&gt;way&lt;/em&gt; more feedback than you anticipated, but because they are all little things, you feel rude saying “no”.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To fix this&lt;/strong&gt;: Build planned contingencies into your estimate. I add a “Technical risk contingency” of between 10% to 20% depending on the level of risk involved. And an “Enhancement contingency” between 10% to 20% depending on how much &lt;a href=&quot;https://www.devtoagency.com/managing-scope-creep/&quot;&gt;scope creep&lt;/a&gt; I feel this client will introduce. These add a buffer or some wiggle room, but you still need to monitor them so it doesn’t go over the allotted time. And this is especially important if &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;charging a fixed price&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;remember-an-estimate-is-an-estimate&quot;&gt;Remember: an estimate is an estimate&lt;/h2&gt;
&lt;p&gt;Last but not least - don’t make the mistake of thinking an estimate is a contract written in blood between you and your client.&lt;/p&gt;
&lt;p&gt;An estimate is just a guide.&lt;/p&gt;
&lt;p&gt;Sure, we all want to get things done on time, and deliver on what we said - but software development is equal parts art and science, and that doesn&amp;#39;t come with 100% guarantees.&lt;/p&gt;
&lt;p&gt;The best you can do is have a plan, communicate early, communicate often, collaborate with your client, and be prepared to make adjustments to the plan as the project evolves.&lt;/p&gt;
</content:encoded></item><item><title>Interview with Neil S Paul from Protorix</title><link>https://www.devtoagency.com/interview-with-neil-paul-from-protorix/</link><guid isPermaLink="false">6326493f38a9cb0001238041</guid><pubDate>Thu, 22 Sep 2022 08:41:40 GMT</pubDate><description>Neil S Paul [https://twitter.com/neilspaul] is a developer and the co-founder of Protorix [https://protorix.com/], a 15-person app development company based in Chennai, India. They have been running for 3 years, and are going from strength to strength. Like many agency founders, Neil learnt his client services skills by freelancing first, and then along with two close friends, doubled down on those skills to build a successful agency. I chatted with Neil to learn more about his story, the sto</description><content:encoded>&lt;p&gt;&lt;a href=&quot;https://twitter.com/neilspaul?ref=devtoagency.com&quot;&gt;Neil S Paul&lt;/a&gt; is a developer and the co-founder of &lt;a href=&quot;https://protorix.com/?ref=devtoagency.com&quot;&gt;Protorix&lt;/a&gt;, a 15-person app development company based in Chennai, India. They have been running for 3 years, and are going from strength to strength.&lt;/p&gt;
&lt;p&gt;Like many agency founders, Neil learnt his client services skills by freelancing first, and then along with two close friends, doubled down on those skills to build a successful agency.&lt;/p&gt;
&lt;p&gt;I chatted with Neil to learn more about his story, the story of Protorix, and to tease out any advice and hints that may be valuable for others to learn.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;1-can-you-introduce-yourself-protorix-to-the-dev-to-agency-readers&quot;&gt;1. Can you introduce yourself &amp;amp; Protorix to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;I am Neil, and I am 24yo. I run a small software dev house Protorix, along with 2 of my partners (Kevin and Jonas). We build custom mobile apps for small and medium businesses using Flutter.&lt;/p&gt;
&lt;h2 id=&quot;2-how-did-protorix-start&quot;&gt;&lt;strong&gt;2. How did Protorix start?&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;We are young and got nothing to lose. Let&amp;#39;s try doing this full-time for a year and see what happens. Nothing to lose, everything to gain&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I&amp;#39;ve been into computers all my life, I got access to my first computer when I was 7, and I built my first ever website when I was 13. I never thought at that point that it would become a big part of my life. Then as time passed, I started freelancing (building small websites) for people in my circle by the time when I was 19. I didn&amp;#39;t know what I was doing, but I got some gigs here and there, and it was good pocket money.&lt;/p&gt;
&lt;p&gt;Then fast forward to mid-2019.&lt;/p&gt;
&lt;p&gt;I was 21 years old, and it was the year of graduation. Since I was already into freelance work, regular jobs and placements didn&amp;#39;t fascinate me. So 2 of my friends (now friends &amp;amp; partners, haha!) and I thought, let&amp;#39;s take a swinger. We discussed this exactly: &amp;quot;We are young and got nothing to lose. Let&amp;#39;s try doing this full-time for a year and see what happens. Nothing to lose, everything to gain&amp;quot;.  &lt;/p&gt;
&lt;p&gt;We rented a house, bought a table, AC, and some chairs, set up the office in a room, and worked from there with our laptops. We also hired 2 of our classmates (I still don&amp;#39;t know why they agreed to join us, lol) to help us. We all had tech backgrounds. 2 - android devs, one backend dev, one web dev, and one designer.&lt;/p&gt;
&lt;p&gt;I still remember sitting on that chair the first day, not knowing what to do.&lt;br&gt;We thought all we needed to know was to code.&lt;/p&gt;
&lt;p&gt;Only at that point, it struck us that we need CLIENTS.&lt;br&gt;That is how Protorix was born!&lt;/p&gt;
&lt;h2 id=&quot;3-do-you-have-a-niche-or-an-ideal-customer-type&quot;&gt;3. Do you have a niche or an ideal customer type?&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;That was our first niche down - we decided we would only build flutter apps.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We had android devs, but we didn&amp;#39;t know how to build iOS apps. We knew we had to figure out a way to develop iOS apps because it would be easier to convince clients when we offered both apps.&lt;/p&gt;
&lt;p&gt;That is when Flutter stable was released. It was still fresh (less than 1-year-old first stable release). We dabbled around using Flutter and instantly knew we had a winner in our hands. It lets us build amazing apps for Android and iOS using a single code base. That was our first niche down - we decided we would only build flutter apps.&lt;/p&gt;
&lt;p&gt;And as time went by, we niched down even further. Now we work predominantly with two types of clients&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Medium/large manufacturing companies that need custom software to manage their processes&lt;/li&gt;
&lt;li&gt;Medium size B2B companies that need custom apps to enhance their products &amp;amp; services.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;We have also worked with government agencies and startups, but most of our clients are in the above-mentioned categories.&lt;/p&gt;
&lt;h2 id=&quot;4-how-did-you-find-your-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;4. How did you find your first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;I used to write answers on &lt;a href=&quot;https://www.quora.com/?ref=devtoagency.com&quot;&gt;Quora&lt;/a&gt; when I was in college and the first client for me as a freelancer, as well as the first client for Protorix as an agency - were both inbound through Quora.&lt;/p&gt;
&lt;p&gt;They saw my answers on Quora, found me on Linkedin, and Boom!&lt;/p&gt;
&lt;h2 id=&quot;5-what-challenges-did-you-face-early-on-and-how-did-you-overcome-them&quot;&gt;5. What challenges did you face early on, and how did you overcome them?&lt;/h2&gt;
&lt;p&gt;Finding clients was a real challenge.&lt;/p&gt;
&lt;p&gt;As time went by, we realized content marketing worked for us all along (starting from Quora). We created a YouTube channel (2k+ subscribers) and an Instagram page (55k+ followers) for Flutter, which drove a lot of traffic to our site.&lt;/p&gt;
&lt;p&gt;We started getting more inbound leads. Even now, more than half of our leads are inbound. Another 30-40% are referrals.&lt;/p&gt;
&lt;p&gt;The second challenge was - figuring out how much to charge and how to set it up. Since we didn&amp;#39;t have any experience previously, we were pulling numbers from thin air. We made many mistakes, undercharged, made losses, and learned from all of that to be at this point today.&lt;/p&gt;
&lt;h2 id=&quot;6-did-you-have-a-clear-vision-of-what-your-business-would-be-when-you-first-started-and-has-that-changed-at-all&quot;&gt;6. Did you have a clear vision of what your business would be when you first started, and has that changed at all?&lt;/h2&gt;
&lt;p&gt;To be honest, we didn&amp;#39;t have any vision for the business in the beginning. We didn&amp;#39;t even know what we were getting into. It all just happened.&lt;/p&gt;
&lt;p&gt;But now we have a goal with every client we sign - BUILD KICKASS APPS&lt;/p&gt;
&lt;h2 id=&quot;7-what-challenges-do-you-face-today&quot;&gt;7. What challenges do you face today?&lt;/h2&gt;
&lt;p&gt;Today, Protorix is more than just 5 friends sitting in a house. We are a team of 15 (12 full-time, 3 part-time)&lt;/p&gt;
&lt;p&gt;Challenges are different - keeping the team happy, making sure everyone sees what I see for the company, managing cash flow cycles (paying salaries on time even if client payments are delayed), and levelling up to bigger clients.&lt;/p&gt;
&lt;h2 id=&quot;8-what-do-you-think-sets-protorix-apart-from-other-agencies&quot;&gt;8. What do you think sets Protorix apart from other agencies?&lt;/h2&gt;
&lt;p&gt;I should say the 3 of us, For the good or bad, we have a pretty high standard for the type of solutions we deliver. We are our own worst critics. There are times when projects have been delayed because we asked our devs and designers to reimplement some of the features and UI in better ways until we are satisfied (delays are not brag-worthy, but it conveys the point 😂)&lt;/p&gt;
&lt;h2 id=&quot;9-what-do-you-hope-your-business-looks-like-in-3-years&quot;&gt;9. What do you hope your business looks like in 3 years?&lt;/h2&gt;
&lt;p&gt;One of the best parts that I love about being an entrepreneur is creating jobs.&lt;/p&gt;
&lt;p&gt;We need to create more jobs, and hopefully, in 3 years Protorix will be a team of 50+ amazing people, doing the same if not better work!&lt;/p&gt;
&lt;h2 id=&quot;10-what-are-3-things-you-would-tell-a-developer-who-is-thinking-of-starting-a-software-agency&quot;&gt;10. What are 3 things you would tell a developer who is thinking of starting a software agency?&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;If you are working a full-time job as a dev, start by transitioning into a freelancer and then start an agency. If you are already a freelancer, you are already halfway there.&lt;/li&gt;
&lt;li&gt;As devs, we usually suck at sales and marketing. Learn sales and marketing before making a full transition. Dev + Sales + Marketing is the holy grail. Don&amp;#39;t make the mistakes I made (Learned it the hard way)&lt;/li&gt;
&lt;li&gt;JUST DO IT! Have the confidence to just do it. Everything else you can figure out as you go!&lt;/li&gt;
&lt;/ol&gt;
</content:encoded></item><item><title>Keeping your clients long-term</title><link>https://www.devtoagency.com/keeping-your-clients-long-term/</link><guid isPermaLink="false">6319332738a9cb0001237ba5</guid><pubDate>Sun, 11 Sep 2022 02:11:14 GMT</pubDate><description>More leads. More sales. More clients. This is the mantra of many agencies, doing everything possible to win new clients. But new clients cost a lot more than existing clients, and depending on which study you believe, a new client project can cost between 5 to 25 as much as a project from an existing client. * You have a whole new relationship to build from scratch * You have an entirely new project to understand and scope * You have a whole new bunch of risks to mitigate Client retention</description><content:encoded>&lt;p&gt;More leads. More sales. More clients.&lt;/p&gt;
&lt;p&gt;This is the mantra of many agencies, doing everything possible to win new clients.&lt;/p&gt;
&lt;p&gt;But new clients cost a lot more than existing clients, and depending on which study you believe, a new client project can cost between 5 to 25 as much as a project from an existing client.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You have a whole new relationship to build from scratch&lt;/li&gt;
&lt;li&gt;You have an entirely new project to understand and scope&lt;/li&gt;
&lt;li&gt;You have a whole new bunch of risks to mitigate&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Client retention is key to a successful thriving agency - especially a smaller agency.&lt;/p&gt;
&lt;p&gt;But building long-term client relationships isn’t always simple, so you need to embrace some strategies and techniques to make it part of your business.&lt;/p&gt;
&lt;h2 id=&quot;offer-the-right-service-%F0%9F%9B%A0&quot;&gt;Offer the right service 🛠&lt;/h2&gt;
&lt;p&gt;If &lt;a href=&quot;https://www.devtoagency.com/think-niche/&quot;&gt;your niche&lt;/a&gt; is “Logo design for small businesses” or “WordPress to Craft CMS Migration”, then your clients are probably not the type to use you more than once or twice.&lt;/p&gt;
&lt;p&gt;That’s ok, as that business model is targeted towards fast-turnaround high-volume work.&lt;/p&gt;
&lt;p&gt;But if you want long-term clients, you need to offer long-term services.&lt;/p&gt;
&lt;p&gt;Custom software fits nicely here, as besides the main build there might be ongoing feature work, &lt;a href=&quot;https://www.devtoagency.com/recurring-revenue/&quot;&gt;ongoing contracts&lt;/a&gt; such as support &amp;amp; maintenance and retainers. As the client&amp;#39;s business grows your work can grow, and it becomes a mutually beneficial relationship.&lt;/p&gt;
&lt;h2 id=&quot;always-think-about-lifetime-value-%F0%9F%92%B8&quot;&gt;Always think about lifetime value 💸&lt;/h2&gt;
&lt;p&gt;That small integration project may just be the tip of the iceberg.&lt;/p&gt;
&lt;p&gt;I had clients that started off with a small job, and eventually lead to high 6-figure jobs within a year or so.  This can happen on all scales - your $300 dollar client can lead to a $3k job - and your $100k project can lead you to a 7-figure project.&lt;/p&gt;
&lt;p&gt;The lifetime value (LTV) of a client is often tricky to determine when you first meet them, and even when you work on the first project for them.&lt;/p&gt;
&lt;p&gt;Million-dollar businesses may never need you again, and that small family-run business may end up being your best client, having new work for you every year.&lt;/p&gt;
&lt;p&gt;As you don’t know in advance your client&amp;#39;s LTV, you should treat every client like they will end up being your best client, with high-quality interactions from day one.&lt;/p&gt;
&lt;p&gt;Moving from a transactional “project-based” mindset to a “longer trusted partner” mindset is the first step you need to take to start retaining your clients.&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t think of short-term projects, think of long-term relationships.&lt;/p&gt;
&lt;h2 id=&quot;truly-understand-your-clients-goals-%F0%9F%8F%86&quot;&gt;Truly understand your client&amp;#39;s goals 🏆&lt;/h2&gt;
&lt;p&gt;Just as your client has a lifetime value to you, you also have a lifetime value for your client.&lt;/p&gt;
&lt;p&gt;To achieve this, you first need to clearly understand their goals.&lt;/p&gt;
&lt;p&gt;I’m not just talking about the goals of this project, I’m talking beyond this project in one, three, or five years’ time&lt;/p&gt;
&lt;p&gt;You need to align yourself as the expert in your field, not just a “dev shop” for hire.&lt;/p&gt;
&lt;p&gt;Don’t think about transactional relationships (what can I get in return), think about what you can do to help this other human.&lt;/p&gt;
&lt;p&gt;A &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;Project Workshop&lt;/a&gt; is a great place for this to happen, a dedicated time where you can understand their past, present, and future goals.&lt;/p&gt;
&lt;p&gt;If you know where they want to go, you can help them get there. Then you’re in a great position to be a long-term strategic partner.&lt;/p&gt;
&lt;h2 id=&quot;make-exceeding-expectations-the-norm-%F0%9F%9A%80&quot;&gt;Make exceeding expectations the norm 🚀&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.devtoagency.com/how-to-meet-your-clients-expectations/&quot;&gt;Meeting your client&amp;#39;s expectations&lt;/a&gt; should be the baseline for any project, and if you consistently do that, there is a good chance they will stick around.&lt;/p&gt;
&lt;p&gt;To &lt;em&gt;make sure&lt;/em&gt; they keep coming back, you want to exceed expectations. This depends a lot on your business and your client, but some examples include.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create an amazing client onboarding experience&lt;/li&gt;
&lt;li&gt;Be exceptionally organised, and be one step ahead of your client&amp;#39;s needs&lt;/li&gt;
&lt;li&gt;Recommend your clients services or products to other contacts&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.devtoagency.com/compete-on-quality/&quot;&gt;Compete on quality&lt;/a&gt; when the others are competing on price&lt;/li&gt;
&lt;li&gt;Deliver the project under the scheduled time (often done via &lt;a href=&quot;https://www.devtoagency.com/managing-scope-creep/&quot;&gt;handing scope creep&lt;/a&gt; well)&lt;/li&gt;
&lt;li&gt;Deliver the project under the estimated budget (if &lt;a href=&quot;https://www.devtoagency.com/pricing-time-and-materials/&quot;&gt;charging time and materials&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Build &lt;a href=&quot;https://www.devtoagency.com/living-user-story-documentation/&quot;&gt;great living documentation&lt;/a&gt; for your client (that becomes a long-term asset)&lt;/li&gt;
&lt;li&gt;Go above and beyond to meet the client&amp;#39;s needs (within reason)&lt;/li&gt;
&lt;li&gt;Provide a free workshop or scoping phase to longtime clients&lt;/li&gt;
&lt;li&gt;Add a bonus feature once the project has been completed (if &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;charging fixed price&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You don’t have to execute all of these all the time, but if you build up these skills slowly you will find going above and beyond is your standard.&lt;/p&gt;
&lt;h2 id=&quot;dont-be-a-penny-pincher-%F0%9F%A4%8F&quot;&gt;Don&amp;#39;t be a penny pincher 🤏&lt;/h2&gt;
&lt;p&gt;When I first started freelancing, I would literally charge for every minute. That’s how it works right?&lt;/p&gt;
&lt;p&gt;After 6 months of working with a great client, they mentioned how I was charging for a “5-minute phone call”, and that they hadn’t experienced that before.&lt;/p&gt;
&lt;p&gt;Instead of building in buffers and contingencies into my estimates, I was literally charging for every minute, and this was affecting our relationship.&lt;/p&gt;
&lt;p&gt;It’s hard to build strong relationships when everything is so transactional, it might work ok for lawyers, but it’s not the norm in other industries.&lt;/p&gt;
&lt;p&gt;So when I started my agency I realised that providing a better estimate (and &lt;a href=&quot;https://www.devtoagency.com/how-to-meet-your-clients-expectations/&quot;&gt;setting better expectations&lt;/a&gt;) meant I didn’t need to charge for every minute. I could ignore the time spent emailing, or on small phone calls and instead, charge more for the actual core value of the project.&lt;/p&gt;
&lt;p&gt;This was a turning point, and when I first realised that client service is a relationship game. If instead of dollars, you obsess over quality relationships and deliverables, then the money will follow.&lt;/p&gt;
&lt;h2 id=&quot;keep-in-touch-%F0%9F%93%9E&quot;&gt;Keep in touch 📞&lt;/h2&gt;
&lt;p&gt;During a project, you communicate with your client a lot.&lt;/p&gt;
&lt;p&gt;But then the project ends, and you get busy with another project. The original client has a whole business to run so they’re busy too, and slowly your communication fades away, and so do the opportunities.&lt;/p&gt;
&lt;p&gt;Make client communication an ongoing part of your business, and not just during a project.&lt;/p&gt;
&lt;p&gt;Don’t do this just to win new business either. Sure, that’s a nice side effect, but remember you’re playing the long game, lifetime value, and this means building actual professional relationships. Even professional friendships.&lt;/p&gt;
&lt;p&gt;Catch up in &lt;a href=&quot;https://www.devtoagency.com/real-life-networking/&quot;&gt;real-life&lt;/a&gt; or virtual (not email), and check how things are going.&lt;/p&gt;
&lt;p&gt;There are so many topics you can talk about.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How&amp;#39;s business? (what do the next 6 months look like)&lt;/li&gt;
&lt;li&gt;How&amp;#39;s the last set of features we worked on going?&lt;/li&gt;
&lt;li&gt;Have you seen XYZ technology?&lt;/li&gt;
&lt;li&gt;Ask for advice, e.g. How does your business manage ZYX?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And this is &lt;strong&gt;very much&lt;/strong&gt; not a one-way street.&lt;/p&gt;
&lt;p&gt;You should share.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your business goals&lt;/li&gt;
&lt;li&gt;New or interesting things you’re doing&lt;/li&gt;
&lt;li&gt;What do the next 6 months look like for you&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;People trust people who share, so put yourself out there.&lt;/p&gt;
&lt;h2 id=&quot;break-your-own-rules-%F0%9F%9A%A8&quot;&gt;Break your own rules 🚨&lt;/h2&gt;
&lt;p&gt;Sometimes, it’s ok to &lt;em&gt;strategically&lt;/em&gt; break your own rules.&lt;/p&gt;
&lt;p&gt;As part of your onboarding, clients need to clearly understand how you work, your processes, and specifically what you don’t do.&lt;/p&gt;
&lt;p&gt;For example, my agency didn’t do production deployments on a Friday, and I let clients know this from the start.&lt;/p&gt;
&lt;p&gt;It was just too risky, and I didn’t want my team working late on a Friday night, or over the weekend to deal with any issues.&lt;/p&gt;
&lt;p&gt;On very rare occasions for specific clients, I would break this rule.&lt;/p&gt;
&lt;p&gt;This would only be a once-a-year type of situation, and only if they were a close client, who had a very important internal reason why they needed to go live on a Friday.&lt;/p&gt;
&lt;p&gt;I don’t recommend this all the time by any means, but on occasion, it served me well and reinforced client relationships.&lt;/p&gt;
&lt;p&gt;Examples include.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Take an emergency call on the weekend&lt;/li&gt;
&lt;li&gt;Work hard to meet a clients deadline&lt;/li&gt;
&lt;li&gt;Fix an issue out of the agreed support window&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I would never work “stupidly hard to meet a deadline” if it was due to scope creep, or even my misestimation. Where I had worked that hard was when the client themselves had a deadline, such as a launch date.&lt;/p&gt;
&lt;p&gt;I would also make it known that it was a very big ask, but that we would try our best because we valued them as a client.&lt;/p&gt;
&lt;p&gt;Again, be sure to do this strategically, and not by default. Otherwise, you will burn out and end up resenting your client - which completely defeats the purpose of trying to retain them.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;In the first couple of years of my agency, I didn&amp;#39;t think about long-term client retention&lt;/p&gt;
&lt;p&gt;Honestly, I was too busy looking for the next project - or having too much work, and being under pressure to quickly finish one project in order to start the next.&lt;/p&gt;
&lt;p&gt;But when I (finally) figured out what &lt;a href=&quot;https://www.devtoagency.com/whats-your-end-goal/&quot;&gt;my end goal&lt;/a&gt; was, I realised to achieve a more relaxed, technically focused, happy, and lucrative agency - I needed a small set of very close clients, not hundreds of different clients with who I only speak once every 2 years when their domain expires.&lt;/p&gt;
&lt;p&gt;So I quadrupled my effort on &lt;em&gt;real&lt;/em&gt; relationship building with my core group of existing clients.&lt;/p&gt;
&lt;p&gt;Focusing on value adds such as support and maintenance contracts and retainers (&lt;a href=&quot;https://www.devtoagency.com/recurring-revenue/&quot;&gt;recurring revenue&lt;/a&gt;!), and also scheduling regular catchups between projects, so both myself and my client always knew what was on the horizon, which allowed scheduling future work a lot easier.&lt;/p&gt;
&lt;p&gt;This was one of the best decisions I could have made for my agency.&lt;/p&gt;
</content:encoded></item><item><title>How to meet your client's expectations</title><link>https://www.devtoagency.com/how-to-meet-your-clients-expectations/</link><guid isPermaLink="false">631861c538a9cb0001237838</guid><pubDate>Wed, 07 Sep 2022 21:54:41 GMT</pubDate><description>We all have our own expectations. When you purchase a pizza you expect it to taste good, to solve your hunger problem, and to arrive quickly. But what if you had never bought a pizza before? Maybe you had never even eaten pizza, and only read about them in books. You might expect a pizza comes whole and you need to slice it yourself. Or you might expect that a pizza is always just tomato and cheese - and be surprised to find out you can actually get meat, mushrooms, or even pineapple on your</description><content:encoded>&lt;p&gt;We all have our own expectations.&lt;/p&gt;
&lt;p&gt;When you purchase a pizza you expect it to taste good, to solve your hunger problem, and to arrive quickly.&lt;/p&gt;
&lt;p&gt;But what if you had never bought a pizza before? Maybe you had never even eaten pizza, and only read about them in books.&lt;/p&gt;
&lt;p&gt;You might expect a pizza comes whole and you need to slice it yourself.&lt;/p&gt;
&lt;p&gt;Or you might expect that a pizza is always just tomato and cheese - and be surprised to find out you can actually get meat, mushrooms, or even pineapple on your pizza.&lt;/p&gt;
&lt;p&gt;Everyone has expectations about everything - and your client is no different.&lt;/p&gt;
&lt;p&gt;They may have never undertaken a digital project before. Or they may have done one previously, but with a development team that worked very differently.&lt;/p&gt;
&lt;p&gt;Understanding and guiding your client&amp;#39;s expectations are important to ensure a successful project delivery. In both your eyes, and in your client&amp;#39;s eyes.&lt;/p&gt;
&lt;h2 id=&quot;you-can%E2%80%99t-meet-expectations-you%E2%80%99re-not-aware-of-%F0%9F%A4%B7%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;You can’t meet expectations you’re not aware of 🤷‍♂️&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Once you feel like you&amp;#39;re being dictated by other people&amp;#39;s expectations, it usually backfires.&lt;/em&gt;” - Rob Zombie, Musician&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You don’t need to meet all your clients expectations, as some could be unrealistic or simply incorrect. But to deliver a “successful” project - you at least need to understand exactly what their initial expectations are.&lt;/p&gt;
&lt;p&gt;The best time to do this with your client is at the very start of the relationship, so a &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;Project workshop&lt;/a&gt; or a discovery call works well.&lt;/p&gt;
&lt;p&gt;At the very start of these discussions, clients will want to talk about the functional requirements they are looking for. The project, the features, the colours etc.&lt;/p&gt;
&lt;p&gt;This is obviously very important, but there are also some more subtle expectations you want to understand.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What is a brief history of their business?&lt;/li&gt;
&lt;li&gt;Why are they looking to solve this now? (why not last year? why not next year?)&lt;/li&gt;
&lt;li&gt;Have they tried any alternatives? And why didn’t they work?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Without asking these questions, you may never know things like “&lt;em&gt;In the next few years our business will be doubling in size&lt;/em&gt;”, so building this project now will help them scale.&lt;/p&gt;
&lt;p&gt;Or you may never know “&lt;em&gt;Actually, our business has been slowly losing money over the last 5 years, so by investing in a new website we really hope to turn that around&lt;/em&gt;”.&lt;/p&gt;
&lt;p&gt;This knowledge is indispensable.&lt;/p&gt;
&lt;p&gt;It also allows you to either make sure you deliver on these expectations, or reset those expectations (more on that later).&lt;/p&gt;
&lt;p&gt;Besides the features, you also want to dig into expectations such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What is the price range they are looking to spend to solve this problem?&lt;/li&gt;
&lt;li&gt;What is the range of time they need this problem solved in?&lt;/li&gt;
&lt;li&gt;Are they looking for an MVP? or something fully featured to last many years?&lt;/li&gt;
&lt;li&gt;With this project, what is the most important element to them,&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Price (getting it done as cheap as possible)&lt;/li&gt;
&lt;li&gt;Time (getting it done as fast as possible)&lt;/li&gt;
&lt;li&gt;Features (getting all the functionality they want)&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;How hands-on can they be during the project (testing etc)&lt;/li&gt;
&lt;li&gt;Do they have any inspiration user interfaces (if a UI based project)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When uncovering this information you shouldn’t interrupt and tell them how you work (yet), as at this stage you simply want to collect the data - and get a baseline of what their expectations are.&lt;/p&gt;
&lt;h2 id=&quot;you-then-need-to-set-and-reset-expectations-%F0%9F%8E%AF&quot;&gt;You then need to set, and reset expectations 🎯&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Expectations are a form of first-class truth: If people believe it, it&amp;#39;s true.&lt;/em&gt;” - Bill Gates&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Once you understand your client&amp;#39;s expectations, you now need to set them (or reset them) to align with&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What’s realistic&lt;/li&gt;
&lt;li&gt;What’s achievable (given their time, or budget constraints)&lt;/li&gt;
&lt;li&gt;How you &lt;em&gt;actually&lt;/em&gt; work&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example, if your client mentioned…&lt;/p&gt;
&lt;p&gt;“&lt;em&gt;&lt;strong&gt;We really only have $X to spend, and want it done by the end of this month&lt;/strong&gt;&lt;/em&gt;”&lt;/p&gt;
&lt;p&gt;You can explain what goes into building their project, and discuss how long other similar projects took to deliver. You can also educate on that custom software is often not “one size fits all”, and that you can’t give a detailed schedule and estimate until you have created a thorough requirements document.&lt;/p&gt;
&lt;p&gt;Or if they said…&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;“The business has been slowly losing money over the last 5 years, so by investing in a new website they really hope to turn that around”&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You should give an honest appraisal of whether you feel the website they have asked for will meet these goals, and if not - suggest some things you feel would help.&lt;/p&gt;
&lt;p&gt;If this was in a discovery call, this is a great time to offer them a longer (paid) scoping workshop where you can take a lot more time to understand their needs, and collaborate to design the best solution.&lt;/p&gt;
&lt;p&gt;Or…&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;“We are really too busy to do any testing, and see this as something you should take care of”&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Then you can discuss how our testing works, and that you need a product owner on their side to complete user acceptance testing after every sprint. Mention how this has huge benefits - and that the industry as a whole now incorporates client testing and sign-off as a standard.&lt;/p&gt;
&lt;p&gt;Educate on how you guide them through this, provide a test plan, and that it’s really not that difficult or time-consuming. Lastly, make sure the client agrees with this before continuing. They need to agree to it in order for it to now become their expectations.&lt;/p&gt;
&lt;p&gt;This is how you recalibrate their original expectations, and set them based on exactly what you will deliver.&lt;/p&gt;
&lt;p&gt;Without this process, your client will go on continuing to think you will because &lt;em&gt;exactly&lt;/em&gt; how they assume, and you might consider the same.&lt;/p&gt;
&lt;p&gt;In the initial phases of a project, there is a lot of expectation setting to be done. This happens in, official documents such as&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your proposal&lt;/li&gt;
&lt;li&gt;Your estimate&lt;/li&gt;
&lt;li&gt;The shared delivery schedule&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But expectations are dynamic, and need to be adjusted throughout the entire project, via&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Managing scope creep&lt;/li&gt;
&lt;li&gt;Weekly check-ins&lt;/li&gt;
&lt;li&gt;Ongoing collaboration&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;Understanding expectations, and correctly setting expectations are key to long-term client relationships.&lt;/p&gt;
&lt;p&gt;It’s also an area where practice makes perfect, so learn from every project, and you will get better at setting and resetting expectations from the start.&lt;/p&gt;
</content:encoded></item><item><title>Your agency's first hire</title><link>https://www.devtoagency.com/your-agencies-first-hire/</link><guid isPermaLink="false">630449ae3fdc7000013d595f</guid><pubDate>Tue, 23 Aug 2022 03:56:50 GMT</pubDate><description>Your first hire will feel like a huge and important decision. You want to get the role exactly right, hire at the perfect time and have “things” in place before you pull the trigger. The thing is - there will never be a perfect time and you will never be completely ready. At some stage, you need to just jump in and only you know when that’s right for you. When not to hire Put simply, when you have very little work, and when you don’t have the experience delivering quality projects on time. H</description><content:encoded>&lt;p&gt;Your first hire will feel like a huge and important decision.&lt;/p&gt;
&lt;p&gt;You want to get the role exactly right, hire at the perfect time and have “things” in place before you pull the trigger.&lt;/p&gt;
&lt;p&gt;The thing is - there will never be a perfect time and you will never be completely ready. At some stage, you need to just jump in and only you know when that’s right for you.&lt;/p&gt;
&lt;h2 id=&quot;when-not-to-hire&quot;&gt;When not to hire&lt;/h2&gt;
&lt;p&gt;Put simply, when you have very little work, and when you don’t have the experience delivering quality projects on time.&lt;/p&gt;
&lt;p&gt;Having too little work means there isn’t even enough for you to do (or make a good wage from), let alone someone else. As a guideline, if half of your week is empty - then you don&amp;#39;t need to worry about hiring just yet.&lt;/p&gt;
&lt;p&gt;Delivering quality projects on time means that you have firsthand experience delivering the quality and standard of work you expect. And you have the personal project management skills to see it through to delivery.&lt;/p&gt;
&lt;p&gt;This is what your agency is about, and you can’t just “buy” that via an employee - it needs to come from the top down. I recommend gaining this experience first, as it will help when you bring other people into the mix.&lt;/p&gt;
&lt;h2 id=&quot;when-to-hire&quot;&gt;When to hire&lt;/h2&gt;
&lt;p&gt;Paying others to help you deliver projects is a core part of building and running an agency. And for this reason, I recommend not leaving it to when you desperately need to hire.&lt;/p&gt;
&lt;p&gt;You don’t want to leave it until you are super busy (60-hour weeks), as onboarding and managing someone at that point will add a lot of additional stress.&lt;/p&gt;
&lt;p&gt;Instead, when you find that 75% of your week (most weeks) is spent delivering projects - that can be a good time to experiment with your first hire.&lt;/p&gt;
&lt;p&gt;I say &amp;quot;experimenting&amp;quot;, because that&amp;#39;s often what your first hire is. There are lots of factors involved in growing your team and finding the right people, and you&amp;#39;re not always in control of all of them. They may not be suitable or they may not enjoy the work. Working with people is never 100% set in stone.&lt;/p&gt;
&lt;h2 id=&quot;contractors-or-full-time&quot;&gt;Contractors or full-time&lt;/h2&gt;
&lt;p&gt;This depends on a lot of factors. If you are experienced managing people, have large ongoing projects, a very full pipeline, and a highly tuned sales funnel - then full-time staff could be a good fit.&lt;/p&gt;
&lt;p&gt;However, if this will be your first foray into management and are not certain about future work past a few months - then contracting is probably a better direction.&lt;/p&gt;
&lt;p&gt;For most new businesses hiring contractors can be best suited, especially at the start.&lt;/p&gt;
&lt;p&gt;This can be on a per-project engagement (e.g. full-time for the next 7 weeks), or it can be ongoing part-time (e.g. 2 days per for 12 months etc), either way, it’s more flexible than a full-time employee, and new agencies often need that flexibility.&lt;/p&gt;
&lt;p&gt;As your business grows you may want the reliability of a full-time employee, especially as valuable knowledge and experience can be lost if contractors move on. But this isn’t a huge concern with your first hire.&lt;/p&gt;
&lt;h2 id=&quot;ease-your-first-hire-in&quot;&gt;Ease your first hire in&lt;/h2&gt;
&lt;p&gt;Bringing someone on a few months before you desperately need to, allows a soft landing pad for all parties involved.&lt;/p&gt;
&lt;p&gt;During this time you can teach the hire about how you work, your standards, processes, and expectations. Taking them through previous projects will be helpful for them to get a visual understanding.&lt;/p&gt;
&lt;p&gt;I’d recommend you take the opportunity to document some of these onboarding procedures, as there is a fair chance you will use them again.&lt;/p&gt;
&lt;p&gt;Leaving hiring for when you are at 100% capacity often creates problems. The onboarding can be missed, and important time for expectation setting and questions are lost.&lt;/p&gt;
&lt;p&gt;You should get them involved in a task of their own quite fast.&lt;/p&gt;
&lt;p&gt;Give them a clear, atomic piece of work to deliver. Not something too complex, and something they can deliver from start to finish. This will give you a clear indication of how they work, and the quality of their work.&lt;/p&gt;
&lt;p&gt;Some examples may be.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A specific page of a website&lt;/li&gt;
&lt;li&gt;The mobile/responsive view of a website&lt;/li&gt;
&lt;li&gt;A certain UI component&lt;/li&gt;
&lt;li&gt;A simple feature&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Don’t time-box them, instead use this as a way to understand how long they take. Make time for them, and let them know you are always there for any question - no matter how silly. Let them know you would prefer they ask a silly question, rather than have a misunderstanding or waste time because they&amp;#39;re blocked.&lt;/p&gt;
&lt;p&gt;Once they have completed this first task, make time to discuss it with them. Let them explain the decisions they made, and any issues they had along the way.&lt;/p&gt;
&lt;p&gt;This initial phase is important for both parties and will allow you to get to know them.&lt;/p&gt;
&lt;h2 id=&quot;what-if-it-doesnt-work-out&quot;&gt;What if it doesn&amp;#39;t work out?&lt;/h2&gt;
&lt;p&gt;Don’t stress, this happens.&lt;/p&gt;
&lt;p&gt;With both contractors and full-time employees, build a “2-week trial” into their engagement. This means that if after that time it’s not working out, then you simply do not need to continue past this point.&lt;/p&gt;
&lt;p&gt;Just make sure you’ve done all you can to set expectations and onboard them. If the problem is on your side, it will just happen again with the next hire.&lt;/p&gt;
&lt;h2 id=&quot;you%E2%80%99ll-learn-a-lot-from-hiring&quot;&gt;You’ll learn a lot from hiring&lt;/h2&gt;
&lt;p&gt;You may not make a lot of money off your first hire (at least initially), but that isn’t always the goal.&lt;/p&gt;
&lt;p&gt;By hiring, you’ll gain the following skills.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Finding and assessing potential workers&lt;/li&gt;
&lt;li&gt;Creating a “brief of work” for someone to clearly understand (in contracting)&lt;/li&gt;
&lt;li&gt;Onboarding hires and teaching your standards and processes&lt;/li&gt;
&lt;li&gt;Communicating with them during development to ensure it&amp;#39;s on track&lt;/li&gt;
&lt;li&gt;Helping them out when needed&lt;/li&gt;
&lt;li&gt;Confirming and testing the work they produce&lt;/li&gt;
&lt;li&gt;Dealing with payments (and perhaps payment negotiation)&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;where-do-i-find-my-first-hire&quot;&gt;Where do I find my first hire&lt;/h2&gt;
&lt;p&gt;Many options - at any one time there are millions of people looking for work. Especially if you’re in the technology industry, and double especially if you hire remote workers.&lt;/p&gt;
&lt;p&gt;To find your first hire you can try the following.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Reach out to your existing &lt;a href=&quot;https://www.devtoagency.com/real-life-networking/&quot;&gt;real-life network&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Use your networks on LinkedIn, Twitter etc&lt;/li&gt;
&lt;li&gt;Job boards (&lt;a href=&quot;https://indeed.com/?ref=devtoagency.com&quot;&gt;Indeed&lt;/a&gt;, &lt;a href=&quot;https://remoteok.com/?ref=devtoagency.com&quot;&gt;RemoteOK&lt;/a&gt; etc.)&lt;/li&gt;
&lt;li&gt;Job board search engine (&lt;a href=&quot;https://jobboardsearch.com/?ref=devtoagency.com&quot;&gt;Job Board Search&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Freelancing sites (&lt;a href=&quot;https://www.notion.so/Your-agencies-first-hire-17dbe9bf15764fdbad117de8eba1375a?ref=devtoagency.com&quot;&gt;Freelancer&lt;/a&gt;, &lt;a href=&quot;https://www.upwork.com/?ref=devtoagency.com&quot;&gt;UpWork&lt;/a&gt;, &lt;a href=&quot;https://www.toptal.com/?ref=devtoagency.com&quot;&gt;TopTal&lt;/a&gt; etc.)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In terms of onshore development vs offshore development - I don’t have any strong opinions.&lt;/p&gt;
&lt;p&gt;Originally all my staff were based in my city, although for the last few years before I sold my agency we did hire a developer in the UK, and that worked well.&lt;/p&gt;
&lt;p&gt;I never hired employees in other countries to save money, but I know many agencies do.&lt;/p&gt;
&lt;p&gt;Most importantly is ensuring high quality - so wherever you hire your team, no matter if they are full-time or contractors, what you want is reliable and efficient work, at a high quality.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Your agency&amp;#39;s first hire is a great milestone - even if it&amp;#39;s just helping out for a few weeks. Hiring and management are integral skills that you will grow over time.&lt;/p&gt;
&lt;p&gt;Hiring and growing my team was one of the favourite parts of my agency. We produced amazing products for our clients, and I forged relationships I will have forever.&lt;/p&gt;
</content:encoded></item><item><title>Real-life networking</title><link>https://www.devtoagency.com/real-life-networking/</link><guid isPermaLink="false">62fe08db3fdc7000013d5635</guid><pubDate>Thu, 18 Aug 2022 09:49:13 GMT</pubDate><description>We live in a digital age, but having a real-life professional network will definitely help your business.</description><content:encoded>&lt;p&gt;We live in a digital age, and if you work in a digital industry it’s easy to think that everyone else does too. But this ain’t the case.&lt;/p&gt;
&lt;p&gt;Millions of businesses operate predominantly IRL (in real life) and are often too busy building their business and making money to be hanging out on the internet.&lt;/p&gt;
&lt;p&gt;They probably won’t see your Google ad, they probably won’t see your blog post, they may never see your LinkedIn message, and they are unlikely to respond to your cold email.&lt;/p&gt;
&lt;p&gt;For these businesses, old-school real-life networking is key.&lt;/p&gt;
&lt;p&gt;So how do you find these businesses?&lt;br&gt;As the saying goes, it’s not what you know - it’s who you know.&lt;/p&gt;
&lt;h2 id=&quot;where-the-big-fish-swim-%F0%9F%90%9F&quot;&gt;Where the big fish swim 🐟&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;Go where the money is... and go there often.”&lt;br&gt;- Willie Sutton, American bank robber&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You can make money on your computer. People can land agency and freelance gigs having never met the person in real life - it happens every day.&lt;/p&gt;
&lt;p&gt;$7,500 custom-built web application, $5,000 WordPress site, $2,500 SEO optimisation package - these are the common types of “internet sales” in the dev agency space, and those prices are pretty average (it’s considerably lower on marketplaces like UpWork).&lt;/p&gt;
&lt;p&gt;But where are those bigger projects?&lt;/p&gt;
&lt;p&gt;Where are the $50k projects, where are the 6-figure projects?&lt;/p&gt;
&lt;p&gt;Of course, big money exists out there, but as you go up in price it gets harder and harder to land them via a cold email, or a sales funnel involving a video and a contact form.&lt;/p&gt;
&lt;p&gt;When dealing with many thousands of dollars, people look to their existing network for referrals and recommendations.&lt;/p&gt;
&lt;h2 id=&quot;build-your-own-professional-network-%F0%9F%91%B7%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;Build your own professional network 👷‍♂️&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;One of the challenges in networking is everybody thinks it&amp;#39;s making cold calls to strangers. Actually, it&amp;#39;s the people who already have strong trust relationships with you, who know you&amp;#39;re dedicated, smart, and a team player, who can help you&lt;/em&gt;”&lt;br&gt;- Reid Hoffman, Co-founder of LinkedIn&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I had an easier start to my agency than many people do - because I built a network.&lt;/p&gt;
&lt;p&gt;My first ever project was landed through my network, my first 6-figure project was via my network, and my first 7-figure project was via my network.&lt;/p&gt;
&lt;p&gt;My professional network consisted of.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;My university nerd friends (one of which was my first co-founder in my agency)&lt;/li&gt;
&lt;li&gt;Colleagues across 4 jobs I had worked in (2 of these were co-founders in other businesses)&lt;/li&gt;
&lt;li&gt;Managers and bosses from those 4 jobs&lt;/li&gt;
&lt;li&gt;Mentors and alumni from a Startup incubator I was in for 4 months&lt;/li&gt;
&lt;li&gt;Clients I’d worked with as a freelancer&lt;/li&gt;
&lt;li&gt;Connections from coding meetups I had attended and spoken at&lt;/li&gt;
&lt;li&gt;People I’d met at coding and tech conferences&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I’d worked professionally in software development for 10 years before my agency, and in that time I had unintentionally built a multi-layered network of people who:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Knew I was a genuine person and a good human being&lt;/li&gt;
&lt;li&gt;Knew I was a talented developer that delivered great work&lt;/li&gt;
&lt;li&gt;Trusted me personally, and trusted my opinion&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you don’t have a professional network, you are playing the game in hard mode.&lt;/p&gt;
&lt;p&gt;Your network can help give advice, find leads (warm leads!), find staff, and even find friendships.&lt;/p&gt;
&lt;p&gt;If you don’t have a professional network, I recommend you start building one today.&lt;/p&gt;
&lt;h2 id=&quot;get-off-your-computer-%F0%9F%9A%B6%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;Get off your computer 🚶‍♀️&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“Rule No. 1: There Are No Facts Inside Your Building, So Get Outside.”&lt;br&gt;― Steve Blank, The Startup Owner&amp;#39;s Manual&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I think too many people rely solely on the magical powers of the internet to start and build their client services business.&lt;/p&gt;
&lt;p&gt;My advice?&lt;/p&gt;
&lt;p&gt;For every day you spend trying to find clients on the net, spend a day building your network - ideally in real life.&lt;/p&gt;
&lt;p&gt;Don’t approach this as simply trying to find clients, people see right through that.&lt;/p&gt;
&lt;p&gt;Sure, finding clients is a great result of a professional network, but often the person you make a connection with is not your client, but a possible referer or a future client.&lt;/p&gt;
&lt;p&gt;Meet people and just be genuine.&lt;/p&gt;
&lt;p&gt;Have conversations with interesting people in your industry, and industries you are interested in. Talk with developers, competitors, and other businesses adjacent to your industry.&lt;/p&gt;
&lt;p&gt;Attend industry meetups, events, and conferences.&lt;/p&gt;
&lt;p&gt;If your local area doesn’t offer this, travel (assuming it’s not too far), or even plan a monthly trip to attend some of these events in a neighbouring (larger) city.&lt;/p&gt;
&lt;p&gt;If you have a business niche in finance, healthcare, startups - whatever - try and get looped into that scene. Go where they go. Learn what they learn, and meet people with no secret motive than to meet them.&lt;/p&gt;
&lt;p&gt;It’s a little old school, but if you meet someone interesting - ask if they have a business card, and give them one of yours (that sentence might show people I’m 40 years old!).&lt;/p&gt;
&lt;p&gt;Follow them on LinkedIn, and shoot them a message saying it was great to meet them, and show that you listened, and are a good human to know.&lt;/p&gt;
&lt;h2 id=&quot;what-a-nice-person-%F0%9F%98%8A&quot;&gt;What a nice person 😊&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“I want to be remembered as a nice person who didn&amp;#39;t hurt people - except my ex-husbands, maybe.” Eugenie Clark&lt;br&gt;― American Shark researcher&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You need to be likeable, respectful, genuine, and interested.&lt;/p&gt;
&lt;p&gt;You don’t have to be super crazy over-the-top nice (in fact don’t be that) - but If people don&amp;#39;t like you, you are going to have a hard time in the agency business.&lt;/p&gt;
&lt;p&gt;Building connections, finding clients, landing jobs, and hiring staff - are all relationship dependant activities, and they are reliant on you being able to form and nurture those relationships.&lt;/p&gt;
&lt;p&gt;Notice I said “interested” not “interesting”?&lt;/p&gt;
&lt;p&gt;Sure it’s great to be an interesting person, but it’s an interested person that other people really like. If you can actually listen and ask questions, then they will walk away from the conversation thinking “Wow, what a nice person!”&lt;/p&gt;
&lt;h2 id=&quot;a-puppy%E2%80%99s-not-just-for-christmas-%F0%9F%90%B6&quot;&gt;A puppy’s not just for Christmas 🐶&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Success is about dedication&lt;/em&gt;”&lt;br&gt;― Usher, Singer &amp;amp; Musician&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It’s called building a network as you need to build it… constantly. You need to care for your relationships, tend to them, and put in the regular effort.&lt;/p&gt;
&lt;p&gt;Meeting an interesting person in your industry (or targeted industry) at a conference is good, reaching out on LinkedIn and getting a chat going is great. Seeing if they want to catch up for a coffee when you’re in the area (your shout!) - that’s fantastic.&lt;/p&gt;
&lt;p&gt;And that’s how it works. You just now need to keep doing it.&lt;/p&gt;
&lt;p&gt;But this isn’t just about meeting new people, it’s about existing relationships too.&lt;/p&gt;
&lt;p&gt;Believe it or not, I’m an introvert.&lt;/p&gt;
&lt;p&gt;I like nothing better than watching TV at home, having a beer with my wife at a quiet pub, or seeing close friends for dinner.&lt;/p&gt;
&lt;p&gt;But I know I need my network, so I put in the work.&lt;/p&gt;
&lt;p&gt;I catch up for coffee, send emails every couple of months, comment on LinkedIn posts, and organise IRL catchups - and it’s now just part of my routine.&lt;/p&gt;
</content:encoded></item><item><title>7 tips for finding your first client</title><link>https://www.devtoagency.com/7-tips-for-finding-your-first-client/</link><guid isPermaLink="false">62eb11d03fdc7000013d4e3f</guid><pubDate>Thu, 04 Aug 2022 00:37:38 GMT</pubDate><description>If you’re just starting with your agency, finding your first client can feel like an impossible task. You know what you want to do. You know you can do it. You just need the chance to prove it, right? I’ve been there, and so have millions of others. So here's some advice that has helped many agencies get started. 1. You probably already know your first client 🤝 There’s a big chance that someone you know, or an associate of someone you know will be your agency's first client. People make the</description><content:encoded>&lt;p&gt;If you’re just starting with your agency, finding your first client can feel like an impossible task.&lt;/p&gt;
&lt;p&gt;You know what you want to do.&lt;br&gt;You know you can do it.&lt;br&gt;You just need the chance to prove it, right?&lt;/p&gt;
&lt;p&gt;I’ve been there, and so have millions of others. So here&amp;#39;s some advice that has helped many agencies get started.&lt;/p&gt;
&lt;h2 id=&quot;1-you-probably-already-know-your-first-client-%F0%9F%A4%9D&quot;&gt;1. You probably already know your first client 🤝&lt;/h2&gt;
&lt;p&gt;There’s a big chance that someone you know, or an associate of someone you know will be your agency&amp;#39;s first client.&lt;/p&gt;
&lt;p&gt;People make the world go round, and from the many agencies I’ve talked to - most people start with a &lt;a href=&quot;https://www.devtoagency.com/referrals-from-friends-and-family/&quot;&gt;referral from someone they know&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Tell everyone you know about your agency and the work you can do. Friends, family, old workmates, school friends, parents of school friends - anyone who will listen.&lt;/p&gt;
&lt;p&gt;Let everyone know on your social networks what you&amp;#39;re doing, share your website, share all updates - and get the word out there.&lt;/p&gt;
&lt;p&gt;When my agency first started, I contacted absolutely everyone I knew and told them what we were doing and asked if they had any work, or knew of anyone that may need our help.&lt;/p&gt;
&lt;p&gt;This got me a few phone calls and coffee meetings - and out of all of that, we got one project. Our first real agency project - a mobile app MVP for a startup.&lt;/p&gt;
&lt;p&gt;Referrals also helped land my agency&amp;#39;s first 7-figure client. So don’t ignore it, and always let people know how you can help them.&lt;/p&gt;
&lt;h2 id=&quot;2-step-away-from-the-screen-%F0%9F%96%A5&quot;&gt;2. Step away from the screen 🖥&lt;/h2&gt;
&lt;p&gt;You can’t always sit behind a computer screen and hope to start a business.&lt;/p&gt;
&lt;p&gt;Many businesses function primarily in the “real world”, and many of these businesses are your potential clients.&lt;/p&gt;
&lt;p&gt;Network in real life. Attend events, meetups, and conferences.&lt;/p&gt;
&lt;p&gt;Meet people, let them know what you do, and build real relationships.&lt;/p&gt;
&lt;p&gt;Don’t go over-the-top selling. Sure, talk about what you do, but also listen to them. Not listening is one of the biggest mistakes you can make in sales.&lt;/p&gt;
&lt;p&gt;There are also more direct real-life methods of getting work.&lt;/p&gt;
&lt;p&gt;Door-to-door sales isn’t dead. Physically visit local businesses, and see if they are looking for your services.&lt;/p&gt;
&lt;p&gt;They may not need you today, but they might tomorrow. Or they may know someone who does.&lt;/p&gt;
&lt;p&gt;One-on-one conversations can do amazing things, and if nothing else, you will get better at pitching your services and more confident selling.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://twitter.com/edanbenatar?ref=devtoagency.com&quot;&gt;Edan Men-Atar&lt;/a&gt; placed road signs at intersections promoting his web design services.&lt;/p&gt;
&lt;p&gt;$450 for 300 signs, and from one sign he landed a $1500 job alone. Pretty great return (and he’s still getting work from these signs!).&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/08/need-a-website-sign-1.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;p&gt;It takes creativity and hustle to build your business, especially in the early stages.&lt;/p&gt;
&lt;h2 id=&quot;3-other-agencies-need-your-help-%F0%9F%99%8B%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;3. Other agencies need your help 🙋‍♂️&lt;/h2&gt;
&lt;p&gt;In the first year of my agency, I emailed other larger digital agencies to let them know we were a small software agency that did web and mobile development. If they had too much work they couldn’t deliver themselves, we could help them out.&lt;/p&gt;
&lt;p&gt;This got us a few projects. They were small and pretty boring - but they brought in money, helped us learn some new technologies, and built relationships with other agencies.&lt;/p&gt;
&lt;p&gt;Many businesses focus solely on overflow work from other businesses, so the market need is out there.&lt;/p&gt;
&lt;p&gt;You can use sites like &lt;a href=&quot;https://clutch.co/?ref=devtoagency.com&quot;&gt;Clutch&lt;/a&gt; to find agencies in your niche, tech, or local area. And luckily every agency website has a contact form - so it’s not hard to talk directly to them.&lt;/p&gt;
&lt;p&gt;Personally, I recommend it as a stepping stone to land your own projects, as I would rather be the one outsourcing than the one outsourced. But work is work, and it’s a great avenue if needed.&lt;/p&gt;
&lt;h2 id=&quot;4-start-with-anything-%F0%9F%91%8F&quot;&gt;4. Start with anything 👏&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.devtoagency.com/think-niche/&quot;&gt;Finding your niche&lt;/a&gt; is a great way to grow an agency, gain expertise, and charge higher rates.&lt;/p&gt;
&lt;p&gt;But you don’t always have the luxury of picking and choosing your projects when you are just getting your business off the ground - and that’s fine.&lt;/p&gt;
&lt;p&gt;Take whatever work you need to pay the bills and keep the lights on.&lt;/p&gt;
&lt;p&gt;In fact, I recommend initially taking many different types of projects, as this can help you gain exposure across different industries and project types (which will help when you niche down).&lt;/p&gt;
&lt;p&gt;And your first projects may be “less than perfect”.&lt;/p&gt;
&lt;p&gt;They may not be as exciting as you want, or in the tech stack that you love - but if you can deliver great work, gain experience, and get your agency rolling - that’s awesome.&lt;/p&gt;
&lt;h2 id=&quot;5-it%E2%80%99s-ok-to-use-marketplaces-%F0%9F%8F%AA&quot;&gt;5. It’s OK to use marketplaces 🏪&lt;/h2&gt;
&lt;p&gt;Many people use marketplaces like &lt;a href=&quot;https://www.upwork.com/?ref=devtoagency.com&quot;&gt;UpWork&lt;/a&gt; or &lt;a href=&quot;https://www.freelancer.com/?ref=devtoagency.com&quot;&gt;Freelancer&lt;/a&gt; - and some people make good money.&lt;/p&gt;
&lt;p&gt;The issue with these businesses is that many people make very little money, and may spend a lot of time pitching for projects they don’t win.&lt;/p&gt;
&lt;p&gt;And that can be ok for a freelancer, but as an agency that is eventually looking to grow, hire, and land bigger jobs - focusing lots of time on these marketplaces can take away time that could be spent landing bigger projects.&lt;/p&gt;
&lt;p&gt;As long as you understand this, and realise there are always people that will do it cheaper than you - but to get your business rolling, do whatever it takes.&lt;/p&gt;
&lt;p&gt;I know people that do well on these marketplaces, but it’s a full-time job. Just like Twitter or any social network - you need to craft the perfect profile to draw people in, and then use authority and social proof to gain their trust. If interested, I recommend checking out &lt;a href=&quot;https://twitter.com/JoshBurnsTech?ref=devtoagency.com&quot;&gt;Josh Burns&lt;/a&gt;, specifically his &lt;a href=&quot;https://youtu.be/Bmu4KznIJoE?ref=devtoagency.com&quot;&gt;YouTube videos&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I would recommend you do everything else AND try these marketplaces at the same time.&lt;/p&gt;
&lt;p&gt;Keep your fingers in many pies, the more pies the more chances of winning.&lt;/p&gt;
&lt;h2 id=&quot;6-it%E2%80%99s-ok-to-work-for-cheap-or-free-%F0%9F%93%89&quot;&gt;6. It’s OK to work for cheap (or free) 📉&lt;/h2&gt;
&lt;p&gt;If you are getting started and have no other projects in your portfolio - then it’s ok to charge whatever you need to charge to win a job. Even if it’s for free.&lt;/p&gt;
&lt;p&gt;I used to be &lt;em&gt;&lt;strong&gt;completely&lt;/strong&gt;&lt;/em&gt; against working for free - but now after talking to many agency founders, I realise sometimes you just need to.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Build your portfolio&lt;/li&gt;
&lt;li&gt;Do good work, and then get referrals&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;But I would say, don’t go straight to “free” - try and charge something (anything) first, free should be a last resort.&lt;/p&gt;
&lt;p&gt;Be 100% sure of the project scope. Ensure the project is clearly defined, and your client understands exactly what you will be delivering. This cannot be something that will drag on forever.&lt;/p&gt;
&lt;h2 id=&quot;7-stick-it-out-%F0%9F%90%98&quot;&gt;7. Stick it out 🐘&lt;/h2&gt;
&lt;p&gt;Most people give up, and most businesses fail - often because people give up.&lt;/p&gt;
&lt;p&gt;Try everything, and if it’s not working, research, study, learn, tweak your pitch - and try again.&lt;/p&gt;
&lt;p&gt;Overnight success stories are bullshit.&lt;/p&gt;
&lt;p&gt;You don’t see the 10 years of battle scars and hard lessons learnt that happened before that overnight success.&lt;/p&gt;
</content:encoded></item><item><title>Your agency's website</title><link>https://www.devtoagency.com/your-agencies-website/</link><guid isPermaLink="false">62dcd5e53fdc7000013d4a6a</guid><pubDate>Tue, 26 Jul 2022 23:39:12 GMT</pubDate><description>You probably know this, but you need a website for your agency. It doesn’t need to be flashy or have lots of content - but you need one. Your website is at the top of your sales funnel, it allows potential clients to: 1. Learn more about what you offer (so they can decide whether it appeals to them) 2. Understand that you can actually do it (via testimonials, case studies, and social proof) 3. Find out what to do next (contact, book a meeting, download a product etc) There are com</description><content:encoded>&lt;p&gt;You probably know this, but you need a website for your agency.&lt;br&gt;It doesn’t need to be flashy or have lots of content - but you need one.&lt;/p&gt;
&lt;p&gt;Your website is at the top of your sales funnel, it allows potential clients to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Learn more about what you offer (so they can decide whether it appeals to them)&lt;/li&gt;
&lt;li&gt;Understand that you can actually do it (via testimonials, case studies, and social proof)&lt;/li&gt;
&lt;li&gt;Find out what to do next (contact, book a meeting, download a product etc)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;There are components on a website these days that are super common on websites for agencies and freelancers - some are obvious like a call to action, but some may be less obvious like testimonials or sign-ups for your newsletter.&lt;/p&gt;
&lt;p&gt;If you’re just getting started, don’t stress.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m going to guide you through the basic components that work well for an agency&amp;#39;s website.  &lt;/p&gt;
&lt;h2 id=&quot;structure-of-a-common-website-%F0%9F%93%9D&quot;&gt;Structure of a common website 📝&lt;/h2&gt;
&lt;p&gt;I don&amp;#39;t think websites should be revolutionary or groundbreaking.&lt;/p&gt;
&lt;p&gt;They should be easy-to-navigate, content driven sites, that get the point across as fast as possible.&lt;/p&gt;
&lt;p&gt;Thousands of businesses have blazed the trail with web design, so we just need to look at what works well.&lt;/p&gt;
&lt;p&gt;Below is a simple wireframe for a single-page website, and I&amp;#39;ll run through what I think are great components to include on your site.&lt;/p&gt;
&lt;p&gt;As it’s just a wireframe, the placement, sizing, amount of content etc is all up to you. This is just a guide. Similarly, as your business grows you may want to add more pages (not just single page), and that&amp;#39;s great.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/07/website-template-1.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;h2 id=&quot;the-header-%F0%9F%8E%A9&quot;&gt;The header 🎩&lt;/h2&gt;
&lt;p&gt;Right at the top of your website, the header should contain your agency&amp;#39;s name, logo if you have one, and a series of links that will take the user further down the page. Nice and simple.&lt;/p&gt;
&lt;p&gt;The header can follow you as you scroll, but if the page isn’t super long it’s not required.&lt;/p&gt;
&lt;h2 id=&quot;the-hero-section-%F0%9F%92%AA&quot;&gt;The hero section 💪&lt;/h2&gt;
&lt;p&gt;The hero is the first thing a visitor sees, it’s the big panel up the top - and often has a big background image or a solid colour that stands out.&lt;/p&gt;
&lt;p&gt;You should have a clear tagline or introduction text, and be super clear about what you do.&lt;/p&gt;
&lt;p&gt;When picking a tagline, you want to make sure your user knows exactly what you do, but also understands how it can value them.&lt;/p&gt;
&lt;p&gt;Many websites just do one or the other, e.g.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Stating what you do&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Mobile Web/App Development For Funded Startups&lt;/li&gt;
&lt;li&gt;Developing delightful apps&lt;/li&gt;
&lt;li&gt;We craft digital experiences that spark joy&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2. Stating how your clients will benefit&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Build and transform your business&lt;/li&gt;
&lt;li&gt;We transform companies&lt;/li&gt;
&lt;li&gt;Turn your idea into a reality&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But I like to combine the two, e.g. “Transform your business with Custom Software.” - this can have the double benefit of showing the client&amp;#39;s needs up front (transforming their business), but also making it crystal clear what you do (Custom software).&lt;/p&gt;
&lt;h2 id=&quot;call-to-action-%F0%9F%92%A5&quot;&gt;Call to action 💥&lt;/h2&gt;
&lt;p&gt;Your website is not only a brochure, it’s also a funnel.&lt;/p&gt;
&lt;p&gt;Strangers find out about your service, then they hit your website, and then they turn into visitors who are now finding out more about you. And when they proceed with your main call to action - they will become leads, who you then try and turn into customers.&lt;/p&gt;
&lt;p&gt;The hero section also includes your call to action. This is the one thing you want every visitor to do, and it should be to contact you.&lt;/p&gt;
&lt;p&gt;You can label it as “Let’s talk” or “Discuss your Project”- whatever you want, but the outcome is the same, you want to talk to them to understand their needs, and ideally land a new client.&lt;/p&gt;
&lt;p&gt;You can have multiple calls to action on a website, for example&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Contact us&lt;/li&gt;
&lt;li&gt;Sign up for our newsletter&lt;/li&gt;
&lt;li&gt;Download our free “Project Planning Checklist”&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But to keep it simple, have one main call to action, and repeat it multiple times.&lt;/p&gt;
&lt;h2 id=&quot;contact-form-%F0%9F%93%A7&quot;&gt;Contact form 📧&lt;/h2&gt;
&lt;p&gt;As you want visitors to contact you, you need a contact form. Having this in a popup is ideal, as you can link to it in multiple places on the webpage - but alternatively, you can have it in the footer and scroll down accordingly.&lt;/p&gt;
&lt;p&gt;Your contact form can be as simple as Name and Email, but I recommend adding more fields to help screen your contacts, and give you more information before you reach out to them.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Full name&lt;/li&gt;
&lt;li&gt;Email address&lt;/li&gt;
&lt;li&gt;Phone number&lt;/li&gt;
&lt;li&gt;Tell us about your project?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can get fancy with questions such as “What is your budget?” (with a select list of budget ranges), but when starting out you want as many enquiries as possible, so keep it simple. The budget question is a great one to add once you are established, as it can help you weed people who want “ &amp;lt; $1000” or whatever your lowest range is.&lt;/p&gt;
&lt;h2 id=&quot;your-services-%F0%9F%9B%A0&quot;&gt;Your services 🛠&lt;/h2&gt;
&lt;p&gt;It may seem obvious, but remember a lot of your clients aren’t technical, so you need to lay out all the services you can offer them, ideally with a small description explaining what they are.&lt;/p&gt;
&lt;p&gt;It’s not all technical either, so don’t just have “Websites, Web apps, and Design”, remember what&amp;#39;s also important to your client.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Scoping and discovery workshops&lt;/li&gt;
&lt;li&gt;Technical consulting&lt;/li&gt;
&lt;li&gt;Legacy system rebuilds&lt;/li&gt;
&lt;li&gt;System integrations&lt;/li&gt;
&lt;li&gt;On-going support and maintenance&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It can be tempting to list technologies in your services, and if you are in a technology niche such as “WordPress Site migrations” or “AWS Infrastructure Setup” then that’s fine - but otherwise, I recommend keeping it general, and free of tech jargon.&lt;/p&gt;
&lt;p&gt;Don’t go overboard with the number of services you list, I recommend no more than 9, but often less is more.&lt;/p&gt;
&lt;h2 id=&quot;case-studies-%F0%9F%93%9A&quot;&gt;Case studies 📚&lt;/h2&gt;
&lt;p&gt;This is where visitors find out you do what you say - by reading more information about a few great projects you have delivered.&lt;/p&gt;
&lt;p&gt;Case studies are integral to building trust and authority. Make sure you pick a few select projects that align with your niche or service. If you don’t have enough, pick the next closest, or simply highlight the parts of the project that most closely align.&lt;/p&gt;
&lt;p&gt;If you are just starting out and have no projects under your belt at all, you will need to be creative. Work on some simple hobby projects to showcase your talents, or even offer to do some heavily discounted (or free) work for businesses to build up a small portfolio.&lt;/p&gt;
&lt;p&gt;You don’t need many, I recommend 3 to 9 case studies showing what you have done for others, and how they benefited.&lt;/p&gt;
&lt;p&gt;Allow the user to click through to a full page (or large popup) where they can read more detail, and get to know more about the client&amp;#39;s needs.&lt;/p&gt;
&lt;p&gt;Your case studies should be structured in the following format.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What was the challenge or problem for your client?&lt;/li&gt;
&lt;li&gt;How you worked alongside the client to devise a plan&lt;/li&gt;
&lt;li&gt;How you successfully implemented and delivered the solution&lt;/li&gt;
&lt;li&gt;The positive impact that solution had on the client&amp;#39;s business&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;In the larger description, you can briefly talk about the technology (such as listing the tech used), but unless you feel it’s very important for your clients to know, there’s really no need to go too deep.&lt;/p&gt;
&lt;p&gt;Demonstrating that you can solve real-world problems for real-world businesses is far more important than what tech stack you used.&lt;/p&gt;
&lt;h2 id=&quot;testimonials-%F0%9F%93%A2&quot;&gt;Testimonials 📢&lt;/h2&gt;
&lt;p&gt;A couple of key testimonials from clients are a great way to show social proof, and also prove you can do what you say you can.&lt;/p&gt;
&lt;p&gt;Video testimonials can also work well, just make sure you collect them at a time just after your client see’s “success”. This isn’t always after go-live, but after they hit one of their own goals - such as saving money, saving time, or making a sale etc.&lt;/p&gt;
&lt;p&gt;If you don’t have any client projects yet, just drop this section. You can’t fake testimonials - and a testimonial from your Mum doesn’t count.&lt;/p&gt;
&lt;h2 id=&quot;logos-clients-or-tech-%F0%9F%92%BC&quot;&gt;Logos (Clients or tech) 💼&lt;/h2&gt;
&lt;p&gt;Showing some key client logos is another great method of social proof, the more recognisable the better. You can see now that you really only need 2 or 3 clients to get good content for your site, as the same businesses can be used for case studies, testimonials, and the client logo section.&lt;/p&gt;
&lt;p&gt;If you&amp;#39;re just starting out and don&amp;#39;t have clients, you can still include this section.&lt;/p&gt;
&lt;p&gt;Instead of client logos, you can still build trust by showing logos of the technologies or software that you leverage, e.g. AWS, JS, Google etc.&lt;/p&gt;
&lt;p&gt;Showing logos of tools you use to help your clients is also valuable from a trust perspective. But if you have them, client logos are more impactful.&lt;/p&gt;
&lt;h2 id=&quot;about-your-agency-%F0%9F%99%8B%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;About your agency 🙋‍♂️&lt;/h2&gt;
&lt;p&gt;Many smaller sites don’t contain an “About” section - but I think they’re missing out.&lt;/p&gt;
&lt;p&gt;People work with people, they don’t work with faceless brands. So show that you’re human, build greater trust, and give a brief sentence about how you got started, why you got started, the beliefs you have, and/or the reason you get up in the morning.&lt;/p&gt;
&lt;p&gt;If you’re a one-person or small agency, you don’t need to say “👋 Hi, I’m Joe!” - although you can if you want. I recommend keeping using the royal “we”, and keeping your options open.&lt;/p&gt;
&lt;h2 id=&quot;optional-newsletter-%F0%9F%97%9E&quot;&gt;Optional: Newsletter 🗞&lt;/h2&gt;
&lt;p&gt;Many visitors may not be ready to “buy” yet (to contact you), but they may want to start a relationship - and a newsletter is a great way to do this.&lt;/p&gt;
&lt;p&gt;You can start collecting email addresses even if you don’t have a newsletter yet. Start when people sign up. And a newsletter doesn’t need to be a huge commitment. Just a once-per-month 500-word update on what your business has been up to, plus a few interesting links in your industry.&lt;/p&gt;
&lt;p&gt;Down the road, if you have more subscribers, and your customers are subscribers, then a newsletter can be a great way to upsell and plant seeds for future work.&lt;/p&gt;
&lt;p&gt;But to begin, all you need is the newsletter signup form and the functionality to store the emails.&lt;/p&gt;
&lt;h2 id=&quot;optional-lead-generation-freebie-%F0%9F%93%9C&quot;&gt;Optional: Lead generation freebie 📜&lt;/h2&gt;
&lt;p&gt;Capturing emails is a great way to have further communication with potential clients, but signing up for a newsletter doesn’t always grab their attention.&lt;/p&gt;
&lt;p&gt;Another option is to give away something digital for free, in return for their email. Most commonly this is a PDF of some sort that will get emailed to them.&lt;/p&gt;
&lt;p&gt;You want to give them something that is of interest, and something that will help them right at this point (they are looking for your services), something such as.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Project planning checklist - 10 things you must do before starting a tech project&lt;/li&gt;
&lt;li&gt;How to scope your own software project&lt;/li&gt;
&lt;li&gt;Writing user stories to describe systems&lt;/li&gt;
&lt;li&gt;Workshop outline: Collecting stakeholder requirements&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Oftentimes you can just give away something that you have built for internal use, for example, a checklist or outline for a workshop.&lt;/p&gt;
&lt;p&gt;Don’t be scared about losing work by giving too much information away. Giving them real value, information and tools to plan their project is a great idea.&lt;/p&gt;
&lt;p&gt;That way if they do reach out, you have already had an influence, and proven your expertise. Plus hopefully, they have a better project plan.&lt;/p&gt;
&lt;h2 id=&quot;optional-blog-%E2%9C%8F%EF%B8%8F&quot;&gt;Optional: Blog ✏️&lt;/h2&gt;
&lt;p&gt;A blog can be great, as it gives you a chance to show your expertise to potential clients - but it’s not mandatory. If you have a blog, then make sure you post at least every 6 months or remove the date so it’s not noticeable that the content is old.&lt;/p&gt;
&lt;p&gt;There’s nothing worse than 3 posts from 2015, then no more content. It makes it look like your agency has died - you&amp;#39;d be better off not having a blog than having a dead blog.&lt;/p&gt;
&lt;p&gt;Your blog shouldn’t be all about technology either but should include topics your client is interested in. Sure they &lt;em&gt;may&lt;/em&gt; be interested in one post about tech, but not 20.&lt;/p&gt;
&lt;p&gt;Write about how software can increase productivity and automate businesses, things they may not know about like “No-code” or “Using Zapier to automate your processes”. Again don’t be afraid of giving away information, if you provide true value to your visitors it will highlight your expertise, and they will remember you.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;competitive-analysis-%F0%9F%93%8A&quot;&gt;Competitive analysis 📊&lt;/h2&gt;
&lt;p&gt;Take a look at other agencies’ websites in your area, niche, or industry, and see if there is anything they are doing that you should be. Sites like &lt;a href=&quot;http://clutch.co/?ref=devtoagency.com&quot;&gt;clutch.co&lt;/a&gt; are great for finding these.&lt;/p&gt;
&lt;p&gt;Remember, most agencies have been around for a while, so you may not have anywhere near the amount of expertise and projects they do. Don’t try and compete, just build the best website you can with what you have.&lt;/p&gt;
&lt;p&gt;I noticed recently many websites have a “Book a meeting” widget instead of a contact form, this allows the client to directly book a time with you for an online call (that integrates into your calendar to show available times).&lt;/p&gt;
&lt;p&gt;This is an example of a relatively new trend - at least for agency websites - so it pays to keep an eye on new concepts and technologies.&lt;/p&gt;
&lt;h2 id=&quot;how-to-build-your-website-%F0%9F%A7%B1&quot;&gt;How to build your website 🧱&lt;/h2&gt;
&lt;p&gt;I’m not going to go into great detail here, but I am going to say - although you may have the skills to develop the website yourself, don’t feel you have to do it from scratch.&lt;/p&gt;
&lt;p&gt;Developers may hate me for this, but in some ways, I feel it’s a waste of time custom building your website in HTML (or worse, React). There are so many great templates out there that can help you get it done super fast, and look great.&lt;/p&gt;
&lt;p&gt;Even though I was a software developer for 20 years, my first agency website was in WordPress, and then later I moved to &lt;a href=&quot;https://carrd.co/?ref=devtoagency.com&quot;&gt;Carrd&lt;/a&gt; which is awesome.&lt;/p&gt;
&lt;p&gt;Keep it simple, especially when starting out.&lt;/p&gt;
&lt;p&gt;Don’t spend 2 months building a website, when you could get something 90% as awesome up in one day. Focus on building your business, not building the perfect website from scratch.&lt;/p&gt;
&lt;p&gt;There are a bunch of great sites that can help you build a website quickly.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://carrd.co/?ref=devtoagency.com&quot;&gt;carrd.co&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://webflow.com/?ref=devtoagency.com&quot;&gt;webflow.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.duda.co/?ref=devtoagency.com&quot;&gt;duda.co&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://wix.com/?ref=devtoagency.com&quot;&gt;wix.com&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;design-%F0%9F%8E%A8&quot;&gt;Design 🎨&lt;/h2&gt;
&lt;p&gt;As a developer, I’m not going to comment too much on web design - but I will say keeping it simple always worked for me.&lt;/p&gt;
&lt;p&gt;I would avoid animations, loading screens, custom cursors etc. Unless you are a design agency, I would focus on clean and functional over highly designed aesthetics.&lt;/p&gt;
&lt;h2 id=&quot;keep-your-website-up-to-date-%F0%9F%A5%B3&quot;&gt;Keep your website up to date 🥳&lt;/h2&gt;
&lt;p&gt;You’ve heard how &amp;quot;The Cobbler&amp;#39;s Children Have No Shoes” right?&lt;/p&gt;
&lt;p&gt;Well, don’t let your agency have a crappy out-of-date website.&lt;/p&gt;
&lt;p&gt;Get in the habit of adding new case studies, testimonials, and logos after the completion of every project - and don’t let your website stagnate.&lt;/p&gt;
&lt;p&gt;As you complete more projects, you can remove case studies that may not be perfect examples of what you want, and only show those that you want more of. This helps make it obvious the types of work you do, and will in turn attract more of those clients.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Your website is the equivalent of a modern-day business card on steroids.&lt;/p&gt;
&lt;p&gt;Make sure it represents your agency, keep it up to date, but don’t waste months trying to make it amazing - as perfect is the enemy of good.&lt;/p&gt;
</content:encoded></item><item><title>5 lessons I learned selling my agency</title><link>https://www.devtoagency.com/5-lessons-i-learned-selling-my-agency/</link><guid isPermaLink="false">62d7b4da3fdc7000013d46d9</guid><pubDate>Wed, 20 Jul 2022 22:26:27 GMT</pubDate><description>My agency was awesome. I enjoyed going to work every day, working with my wife every day, and was really proud of our highly skilled team. We had awesome clients and we were growing year on year. But even though I got so much out of it, I had run my agency for most of my 30s - and I wanted different experiences out of my 40s. Selling wasn’t my master plan by any means, but it was a nice way to end a great experience - plus give both my staff and clients a good &quot;new home&quot;. I thought it might</description><content:encoded>&lt;p&gt;My agency was awesome.&lt;/p&gt;
&lt;p&gt;I enjoyed going to work every day, working with my wife every day, and was really proud of our highly skilled team. We had awesome clients and we were growing year on year.&lt;/p&gt;
&lt;p&gt;But even though I got so much out of it, I had run my agency for most of my 30s - and I wanted different experiences out of my 40s.&lt;/p&gt;
&lt;p&gt;Selling wasn’t my master plan by any means, but it was a nice way to end a great experience - plus give both my staff and clients a good &amp;quot;new home&amp;quot;.&lt;/p&gt;
&lt;p&gt;I thought it might be interesting to share some of the lessons I learned selling my development agency.&lt;/p&gt;
&lt;h2 id=&quot;1-anyone-can-sell-even-small-businesses-%F0%9F%91%A8%E2%80%8D%F0%9F%92%BC&quot;&gt;1. Anyone can sell, even small businesses 👨‍💼&lt;/h2&gt;
&lt;p&gt;I used to think only product businesses could be acquired, and you needed a SaaS bringing in a good MRR in order for the business to actually be worth anything.&lt;/p&gt;
&lt;p&gt;If you Google &amp;quot;selling an agency&amp;quot;, it&amp;#39;s not always positive stories, and it can scare you off with the number of people talking about how hard it is.&lt;/p&gt;
&lt;p&gt;But I can tell you first-hand that it&amp;#39;s not always as hard as you hear or read about. So if this is something you ever want to do, it’s certainly possible.&lt;/p&gt;
&lt;p&gt;You also don’t need to be doing $10M a year in order for another company to acquire yours - there are many reasons why acquisitions and mergers take place, and they are often more about strategy than your bottom line.&lt;/p&gt;
&lt;h2 id=&quot;2-it%E2%80%99s-a-slow-process-%F0%9F%95%93&quot;&gt;2. It’s a slow process 🕓&lt;/h2&gt;
&lt;p&gt;Selling a business isn&amp;#39;t usually quick.&lt;/p&gt;
&lt;p&gt;For me, it took around 20 months from initial conversations, to reviewing the contract, to signing the contract. Although we did have a small global pandemic right in the middle that made things take a little longer!&lt;/p&gt;
&lt;p&gt;It’s also not a guaranteed process. There are many points along the road where either the buyer or the seller might bail out. Due diligence, contract negotiation, price negotiation, transition agreements. It’s common that deals never go through, even after a lot of time and effort has been spent by both parties.&lt;/p&gt;
&lt;p&gt;Seeing friends who had gone through this process (successfully or unsuccessfully), and seeing how long it took - made me wary about even thinking about selling.&lt;br&gt;I was just too busy running a successful business.&lt;/p&gt;
&lt;p&gt;But ultimately that stood in my favour, because I was never desperate to sell, my business was going great, and I knew I didn’t want to get bogged down with lengthy contract negotiations.&lt;/p&gt;
&lt;p&gt;Because of this, I approached the whole process very transparently about what would work and what would not work for my wife and I.&lt;/p&gt;
&lt;p&gt;So even though it did take a while, the process ran rather smoothly.&lt;/p&gt;
&lt;h2 id=&quot;3-simplicity-makes-things-simpler-%F0%9F%A7%98%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;3. Simplicity makes things simpler 🧘‍♂️&lt;/h2&gt;
&lt;p&gt;My wife and I are simple, organised people.&lt;/p&gt;
&lt;p&gt;We are minimalists, we track our finances (down to the cent!), don’t like overcomplicating things, and have never taken on any debt. And we built our business in the same way.&lt;/p&gt;
&lt;p&gt;These attributes played in our favour when it came to selling:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The business structure was simple - my wife and I 50/50&lt;/li&gt;
&lt;li&gt;Our balance sheet was very clean, and we’d never taken on debt&lt;/li&gt;
&lt;li&gt;We had very low overheads (staff, rent, and a few monthly SaaS bills)&lt;/li&gt;
&lt;li&gt;We had no long-term liabilities (we worked from a co-working space)&lt;/li&gt;
&lt;li&gt;We had a small list of very well-paying clients (as opposed to many low-paying clients)&lt;/li&gt;
&lt;li&gt;Our clients owned all their code, IP, assets etc&lt;/li&gt;
&lt;li&gt;All clients were on an ongoing contract (either retainer or support &amp;amp; maintenance)&lt;/li&gt;
&lt;li&gt;We had very thorough documentation on all our projects&lt;/li&gt;
&lt;li&gt;We had a lean team of high-performing people&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If instead we had 4 business partners, 45 staff members, and 117 clients - the process would have been a lot more complicated for sure.&lt;/p&gt;
&lt;h2 id=&quot;4-it%E2%80%99s-about-today-but-also-the-future-%F0%9F%9A%80&quot;&gt;4. It’s about today, but also the future 🚀&lt;/h2&gt;
&lt;p&gt;If you’re selling a business, obviously the performance history of your company matters.&lt;/p&gt;
&lt;p&gt;Year-on-year growth, low expenses, and high profit are all these are fantastic for your business, but you’re not being acquired &lt;em&gt;solely&lt;/em&gt; based on what’s happened historically - but on what the acquisition brings in the future.&lt;/p&gt;
&lt;p&gt;In any business, especially a service business - relationships, and stability are key.&lt;/p&gt;
&lt;p&gt;If the staff and the clients don’t want to move with the sale, then that’s usually a dealbreaker.&lt;/p&gt;
&lt;p&gt;By the time I sold we had 8 large long-term projects and ongoing retainers or support &amp;amp; maintenance contracts with all clients. These were all custom software development projects, that powered their businesses and required ongoing work.&lt;/p&gt;
&lt;p&gt;Whilst ongoing contracts are awesome, they are not the only way to show reliable revenue.&lt;/p&gt;
&lt;p&gt;A successful marketing funnel and sales pipeline can be a huge asset for the purchasing business, especially if it’s a standard operating process that can scale.&lt;/p&gt;
&lt;p&gt;If my agency had a portfolio of 150 marketing websites, no ongoing client contracts, very few updates per year, and no real sales pipeline - it would have been a much harder sell.&lt;/p&gt;
&lt;p&gt;You need to be able to prove reliable recurring revenue, even after the acquisition and merger have taken place, and you have left the business.&lt;/p&gt;
&lt;h2 id=&quot;5-strategy-can-be-more-important-than-revenue-%F0%9F%A4%94&quot;&gt;5. Strategy can be more important than revenue 🤔&lt;/h2&gt;
&lt;p&gt;Profit is awesome, and your services are awesome. But it’s not always enough for a business to deal with the overhead of acquiring another business.&lt;/p&gt;
&lt;p&gt;Acquisitions and mergers are strategic events, and it’s usually a combination of factors that make your business interesting to purchase.&lt;/p&gt;
&lt;p&gt;For me, having some well-known brands in our portfolio definitely made a difference. I’m not talking Coca-Cola or Tesla. But companies already known to the potential acquirer can definitely make the purchase more enticing.&lt;/p&gt;
&lt;p&gt;Every business has a different long-term strategy, and purchasing a smaller business is often easier and quicker than building up those skills internally.&lt;/p&gt;
&lt;p&gt;For example, a no-code agency with a large client in the pharmaceutical industry could be a strategic acquisition for a digital agency wanting to get into no-code and the pharmaceutical space.&lt;/p&gt;
&lt;p&gt;Or a custom software agency with a niche in the financial services sector could be a potential acquisition for a large financial services firm, who are wishing to bring a skilled team in-house to work internally.&lt;/p&gt;
&lt;p&gt;Or a medium-sized digital agency may want to double in size over the next few years. So purchasing another smaller development company may be the best way to make this happen.&lt;/p&gt;
&lt;p&gt;There are countless ways strategy plays a role.&lt;br&gt;Revenue is great, but the strategy is usually the deciding factor.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;You may be happy running your agency for many more years, but even still - it’s always good to think about an exit strategy - one that aligns with your end goal.&lt;/p&gt;
</content:encoded></item><item><title>Managing scope creep</title><link>https://www.devtoagency.com/managing-scope-creep/</link><guid isPermaLink="false">62c0e8993fdc7000013d3c9f</guid><pubDate>Wed, 13 Jul 2022 01:47:00 GMT</pubDate><description>Scope creep. Two words that send a shiver down the spine of anyone who works in client services. When managed correctly, scope creep stays in its box, the project gets delivered as planned, and everyone's happy. But unfortunately scope creek does happen, and most people don’t manage it very well. In fact, it's a huge problem (according to the PMI Pulse report [https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse-of-the-profession-2017.pdf] ) * 50% of</description><content:encoded>&lt;p&gt;Scope creep. Two words that send a shiver down the spine of anyone who works in client services.&lt;/p&gt;
&lt;p&gt;When managed correctly, scope creep stays in its box, the project gets delivered as planned, and everyone&amp;#39;s happy.&lt;/p&gt;
&lt;p&gt;But unfortunately scope creek does happen, and most people don’t manage it very well.&lt;/p&gt;
&lt;p&gt;In fact, it&amp;#39;s a huge problem (according to the &lt;a href=&quot;https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse-of-the-profession-2017.pdf?ref=devtoagency.com&quot;&gt;PMI Pulse report&lt;/a&gt;)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;50% of projects experience scope creep&lt;/li&gt;
&lt;li&gt;Only 57% finish within the estimated budget&lt;/li&gt;
&lt;li&gt;And only 51% finish on the estimated schedule&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Successfully managing scope creep is sometimes the difference between succeeding in client services, and deciding to give up altogether and find a 9-5 job.&lt;/p&gt;
&lt;h2 id=&quot;why-is-scope-creep-a-problem-%F0%9F%A4%B7%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;&lt;strong&gt;Why is scope creep a problem? 🤷‍♂️&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Assumptions are the termites of relationships&lt;/em&gt;”&lt;br&gt;- Henry Winkler, Actor&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Scope creep, requirement creep, or feature creep - whatever you call it, it&amp;#39;s when the requirements of a project change during the delivery phase, affecting both the budget and schedule of the project - which for the client are two of the most important factors.&lt;/p&gt;
&lt;p&gt;But the worst part about scope creep is that it leaves everyone unhappy.&lt;/p&gt;
&lt;p&gt;For you, it can be frustrating having a client continuously change requirements, and for the client, it’s frustrating hearing that their project won’t be delivered on time or on budget.&lt;/p&gt;
&lt;h2 id=&quot;how-does-scope-creep-occur-%F0%9F%A4%A6%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;&lt;strong&gt;How does scope creep occur? 🤦‍♂️&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Clear thinking requires courage rather than intelligence&lt;/em&gt;”&lt;br&gt;- Thomas Szasz, Academic and psychiatrist&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Ask any agency or freelancer, and they’ll tell you scope creep occurs when clients say things like…&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;“That looks great, but could we also now add…”&lt;/li&gt;
&lt;li&gt;“Now that Jane has seen this, she was thinking we should…”&lt;/li&gt;
&lt;li&gt;“I just noticed this other website has X, and I would like to add…”&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And that’s definitely one type of scope creep, when the client changes their mind.&lt;/p&gt;
&lt;p&gt;But remember just because the client asks for something, doesn’t mean the scope has changed. The project scope is really just an agreement of what will be delivered, so it can’t just change without both parties agreeing.&lt;/p&gt;
&lt;p&gt;But there are some other types of scope creep, where the size of the project increases without you initially realising.&lt;/p&gt;
&lt;p&gt;Miscommunication can mean missing requirements, or failing to fully understand what the client has asked for. For you, this feels like scope creep, but not to your client. Similarly, unexpected complexity can make the project balloon well past what you thought the initial scope was (e.g. realising you now have to implement your own scheduling system, because you thought a third-party API handled it when it doesn’t).&lt;/p&gt;
&lt;p&gt;So scope creep comes in a few shapes and sizes.&lt;/p&gt;
&lt;p&gt;I believe there are 5 key reasons why 50% of projects are affected by scope creep.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Unclear project requirements&lt;/li&gt;
&lt;li&gt;Failure to set expectations&lt;/li&gt;
&lt;li&gt;Unexpected complexity&lt;/li&gt;
&lt;li&gt;No planned contingency&lt;/li&gt;
&lt;li&gt;Saying “Ok” to everything&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Let’s dive into each of these, and talk about how to manage them effectively.&lt;/p&gt;
&lt;h2 id=&quot;how-to-manage-scope-creep&quot;&gt;&lt;strong&gt;How to manage scope creep&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Ch-ch-changes (Turn and face the strain)&lt;/em&gt;&lt;br&gt;&lt;em&gt;Ch-ch-changes (Where&amp;#39;s your shame, you&amp;#39;ve left us up to our necks in it)&lt;/em&gt;”&lt;br&gt;- David Bowie, Changes&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;1-set-clear-project-requirements-%F0%9F%93%9D&quot;&gt;1. Set clear project requirements 📝&lt;/h2&gt;
&lt;p&gt;Miscommunication between what the client asks for, and what you understand, is a central source of scope creep. You can debate forever whether they told you they “wanted their logo to spin” or not, but if they say they said it, and you say you didn’t hear it - then that’s a problem.&lt;/p&gt;
&lt;p&gt;Miscommunication can also be sneakier.&lt;/p&gt;
&lt;p&gt;For example, your client requests that “When X happens we get a notification” so you add that as a requirement, and start the project. But it’s not until they actually see the feature two months later that you realise they expected a Slack notification, not an email. They didn&amp;#39;t say, and you didn&amp;#39;t ask.&lt;/p&gt;
&lt;p&gt;There’s no room for assumptions in successful projects, and ambiguous requirements need to be further clarified.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5 ways to make sure you set precise requirements:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Be super detailed with the requirements documentation. I use &lt;a href=&quot;https://www.devtoagency.com/living-user-story-documentation/&quot;&gt;living user story documentation&lt;/a&gt; for this.&lt;/li&gt;
&lt;li&gt;Have a requirement confirmation session with your client, where you run through all requirements and agree to “sign them off” to officially confirm understanding. I do this in a follow-up after the &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;project workshop&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Use the signed-off requirements as the line items in your estimation, which you also send to your client to review.&lt;/li&gt;
&lt;li&gt;Break the project into small sprints (I do 2 weeks), and before starting a sprint hold a sprint kickoff session to re-run through and confirm the exact requirements in that sprint.&lt;/li&gt;
&lt;li&gt;When your client is testing a sprint, give them a document with the exact confirmed requirements to test.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Adding these checks and balances helps catch any unclear requirements early, and hopefully before you start any real work.&lt;/p&gt;
&lt;p&gt;But accurate requirements also rely on strong communication, as they may need to be re-confirmed throughout the development phase.&lt;/p&gt;
&lt;p&gt;Always make sure everything is clearly communicated, and that there is a paper trail about the decision. I recommend summarising in an email, even if the conversation took place out of email, and always ensure requirements are updated in one central single source of truth.&lt;/p&gt;
&lt;h2 id=&quot;2-set-expectations-%F0%9F%A4%9D&quot;&gt;2. Set expectations 🤝&lt;/h2&gt;
&lt;p&gt;If the first time your client understands how you handle scope creep, is when the scope has started creeping - then you’ve done it wrong.&lt;/p&gt;
&lt;p&gt;Your way of working should be communicated from the first time you meet a client, and re-enforced often, especially at the start of a relationship.&lt;/p&gt;
&lt;p&gt;What do I mean by “your way of working”?&lt;/p&gt;
&lt;p&gt;I mean your standards and processes.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How you gather requirements and scope projects&lt;/li&gt;
&lt;li&gt;How you price your project&lt;/li&gt;
&lt;li&gt;How you deal with new feature requests&lt;/li&gt;
&lt;li&gt;How you deal with unexpected changes&lt;/li&gt;
&lt;li&gt;How you manage communication&lt;/li&gt;
&lt;li&gt;How you manage the project&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Your client is looking for an expert to guide them, and your standards and processes are the way you ensure a quality project delivery. And that’s great because that’s exactly how you set clear expectations.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5 ways to make sure you have set expectations:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;From your very first interaction, or the “sales dance” as I like to call it, tell your client how you work. Educate them, as they may never have embarked on a project like this before.&lt;/li&gt;
&lt;li&gt;A &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;project workshop&lt;/a&gt; is the next place to communicate what they should expect when choosing you to deliver their project. As this is a longer session you can go into much more detail.&lt;/li&gt;
&lt;li&gt;Your proposal for the project should enforce how you work. In fact, I always included a 3 page “How we work” at the end of every proposal (just in case it wasn’t clear by this stage)&lt;/li&gt;
&lt;li&gt;Once a client accepts your proposal, again it’s best to do a quick run-through (in person or on a call) of how it’s going to work. Remember, people don’t always read everything you give them.&lt;/li&gt;
&lt;li&gt;Be consistent with describing your processes the entire way through your project. Sprint kickoff, retrospective, and any other further client meetings.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;3-avoid-unexpected-complexity-%F0%9F%9B%A0&quot;&gt;3. Avoid unexpected complexity 🛠&lt;/h2&gt;
&lt;p&gt;Easier said than done, as the problem here is the “unexpected” part.&lt;/p&gt;
&lt;p&gt;Unexpected complexity is when something turns out to be more involved than you initially anticipated. So whilst this is scope creep for you (things just for a lot harder), your client doesn’t think it’s scope creep. So this can be a tricky one to handle.&lt;/p&gt;
&lt;p&gt;But there are definitely ways to mitigate unexpected complexity and reduce the chances of it occurring in your project.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5 ways to avoid unexpected complexity:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Simply avoid complexity, and you’ll avoid unexpected complexity. By &amp;quot;dumbing down&amp;quot; things as much as possible, there are fewer hidden cracks for unexpected complexity to hide. Prioritise clean and maintainable instead of over-engineered.&lt;/li&gt;
&lt;li&gt;Use trusted tools. Don’t decide that this project is a great time to try that cutting-edge technology. Don’t make your client your guinea pig - do that on your own internal projects.&lt;/li&gt;
&lt;li&gt;Conduct thorough research on things you haven’t used before. Read the documentation, reviews, and outstanding Github issues. Do everything you can to confirm it’s the right choice.&lt;/li&gt;
&lt;li&gt;If you need, create a simple prototype to confirm assumptions. Be transparent with your client, and do this as a standalone mini project, as their project success may depend on this prototype working as expected.&lt;/li&gt;
&lt;li&gt;Do the riskiest or more complex parts right upfront. Even if you built a prototype, when developing the project front-load the riskiest parts. Don’t always start with the “Login” screen and work from there. Whilst this doesn’t directly avoid complexity, you will find unexpected issues much sooner- which will give you a lot more options on how to proceed.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;4-build-in-a-planned-contingency-%F0%9F%93%8A&quot;&gt;4. Build in a planned contingency 📊&lt;/h2&gt;
&lt;p&gt;If you read my article on my &lt;a href=&quot;https://www.devtoagency.com/pricing-hybrid/&quot;&gt;hybrid pricing approach&lt;/a&gt;, you will see I build two contingencies into a project. Technical risk contingency, and project enhancement contingency.&lt;/p&gt;
&lt;p&gt;Software development is not an exact science, so I add multiple layers of contingency and buffer to provide the best chance of success. By not adding any contingencies into the cost and schedule you provide your client, you are simply asking for trouble.&lt;/p&gt;
&lt;p&gt;You always hear the phrase &amp;quot;underpromise and overdeliver&amp;quot; right? Here’s how you do that.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5 ways to include planned contingencies:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Build a technical risk contingency of 10%-20% into the project. Base this amount on how “risky” this project is to deliver from a technical standpoint, e.g. how much of the tech you have never used before.&lt;/li&gt;
&lt;li&gt;Add a project enhancement contingency of between 10%-20%, to allow your client to add “scope creep” without affecting the time or cost. Base this amount on the chances of this client requesting changes. If you haven’t worked with them before, go higher as opposed to lower.&lt;/li&gt;
&lt;li&gt;Add a buffer to the external project schedule you give your client. Allow yourself extra time for everything. E.g on a 2 month project I would allow 1 week, meaning you get things done 1 week earlier than when you show the client, you can then eat into this buffer if you need to and not be so rushed.&lt;/li&gt;
&lt;li&gt;Nothing is set in stone. I always reminded my clients that an “estimated delivery date” is exactly that, an estimate. If they need to plan a press release or a launch party, then I suggest they do it a week or two after what we plan. Why would you add undue stress when it’s not needed.&lt;/li&gt;
&lt;li&gt;If a client has a fixed budget that cannot budge, I recommend they only spend 80% of it, even with the other contingencies above. Remind them of the statistics around how many projects go over time and budget. This is not your fault, it&amp;#39;s the whole software development industry, and it&amp;#39;s better to be safe than sorry.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;5-don%E2%80%99t-just-say-%E2%80%9Cok%E2%80%9D-to-everything-%F0%9F%A4%94&quot;&gt;5. Don’t just say “Ok” to everything 🤔&lt;/h2&gt;
&lt;p&gt;If you’ve implemented all of the previous steps, and your client still demands that they asked for “Login with Google Account” but somehow it wasn’t captured in the requirements (or any of the requirement review sessions) - then what happens next is up to you.&lt;/p&gt;
&lt;p&gt;If you just say “Ok”, and start working on it, then that will affect the schedule. And if you choose to charge for that, then it affects the client&amp;#39;s price (and if you don’t it affects your budget).&lt;/p&gt;
&lt;p&gt;But you have the signed-off requirements from the scoping phase and the estimate, you’ve set expectations the whole time, and let them know that anything not in the requirements will not be included.&lt;/p&gt;
&lt;p&gt;So you didn’t “miss” this feature… everyone missed it.&lt;/p&gt;
&lt;p&gt;In fact, as this is their project, and they knew they wanted that feature - it is actually more in their court than yours.&lt;/p&gt;
&lt;p&gt;But none of that really matters, as you want to keep your client relationship strong, so it’s never time to blame people.&lt;/p&gt;
&lt;p&gt;Hopefully, you have the project enhancement contingency built into your time and cost, so you can use that if needed. But assuming you don’t, or assuming you&amp;#39;ve already used it all - there are options other than just saying “Ok” and adding it into scope.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5 ways to avoid just saying OK to scope creep:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Scope the new features with your client, estimate them, and then put them in the project backlog.&lt;/li&gt;
&lt;li&gt;The project enhancement contingency can then be used to accommodate some or all of the backlog items (depending on how much there is and how many new features there are). This won’t affect the price or schedule, as it was already considered upfront.&lt;/li&gt;
&lt;li&gt;Backlog items can be paid for individually by the client on a time and materials basis.&lt;/li&gt;
&lt;li&gt;Backlog items can be left for now, and bundled into a future “Version 2” of the project to be booked separately. This is my preferred approach, and again you can set expectations with a client up front that 90% of projects end up having multiple versions, so they don’t need to do it all now.&lt;/li&gt;
&lt;li&gt;You can offer a discount for any new features. This is a compromise, as the price and time will still increase, but you share the increase. Only do this if you do feel like a mistake happened and something was missed in the requirements, this should not be a common occurrence.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;my-experience-with-scope-creep-%F0%9F%93%A2&quot;&gt;&lt;strong&gt;My experience with scope creep 📢&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Experience is a great teacher&lt;/em&gt;”&lt;br&gt;- John Legend, American singer-songwriter&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;When starting out, I had to learn the hard way - I guess most people do.&lt;/p&gt;
&lt;p&gt;Clients would ask for additional things, and sometimes I would do them for free. This seemed fine when starting out, especially when starting a new project.&lt;/p&gt;
&lt;p&gt;Early on my requirements were probably a little too vague, some parts were ambiguous, and maybe a feature got missed here or there. You’re excited to get started, so it makes sense why this happens.&lt;/p&gt;
&lt;p&gt;It took me about 6 months before I found the processes to help mitigate scope creep - but honestly - it was always a work in progress, and the contents of this article were 8 years in the making.&lt;/p&gt;
&lt;p&gt;I think one of the key ways I avoided scope creep was to move clients to an &lt;a href=&quot;https://www.devtoagency.com/recurring-revenue/#retainers-%F0%9F%94%84&quot;&gt;ongoing monthly retainer&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Retainers can make the process more flexible, as with an agreed number of hours per month, it’s really up to the client what we should spend that on. If they change their mind and now want their “logo to spin” - no worries, that will take time away from another feature (that will have to wait until next month).&lt;/p&gt;
&lt;p&gt;But whilst retainers can make it a little easier, scope creep can still happen. It’s really just part of the game.&lt;/p&gt;
&lt;p&gt;So do the best you can to have systems and processes in place to mitigate scope creep from occuring, and then if it does occur - do the best you can to deal with it as fast as possible.&lt;/p&gt;
&lt;p&gt;Keep learning, keep experimenting, and you’ll keep improving.&lt;/p&gt;
</content:encoded></item><item><title>Why agencies can thrive during a recession</title><link>https://www.devtoagency.com/why-agencies-can-thrive-during-a-recession/</link><guid isPermaLink="false">62c2688f3fdc7000013d3d3e</guid><pubDate>Mon, 04 Jul 2022 04:29:47 GMT</pubDate><description>Recessions come and go, but when they hit, businesses tighten their belts. They reassess what’s integral, and move from “business as usual” mode, to “survival” mode. But unlike some other industries, agencies and freelancers have a unique opportunity in a recession. Employees are an ongoing expense, processes need to be automated, and integral software still needs support and maintenance - and agencies can help with all of that. Now I’m not saying agencies are recession-proof, but I am saying</description><content:encoded>&lt;p&gt;Recessions come and go, but when they hit, businesses tighten their belts.&lt;/p&gt;
&lt;p&gt;They reassess what’s integral, and move from “business as usual” mode, to “survival” mode.&lt;/p&gt;
&lt;p&gt;But unlike some other industries, agencies and freelancers have a unique opportunity in a recession. Employees are an ongoing expense, processes need to be automated, and integral software still needs support and maintenance - and agencies can help with all of that.&lt;/p&gt;
&lt;p&gt;Now I’m not saying agencies are recession-proof, but I am saying that as other businesses adjust to economic changes - agencies can benefit.&lt;/p&gt;
&lt;h2 id=&quot;agencies-can-be-more-affordable-%F0%9F%92%B8&quot;&gt;Agencies can be more affordable &lt;strong&gt;💸&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;When businesses are cutting costs, they often look to full-time employees as the first area to cut back on.  And agencies can be a cost-effective alternative.&lt;/p&gt;
&lt;p&gt;And whilst agencies may cost more &lt;em&gt;per hour&lt;/em&gt; that a full-time employee, that&amp;#39;s only one aspect of affordability.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You only pay for the services you need (e.g. one project)&lt;/li&gt;
&lt;li&gt;You only pay when you need them (e.g. X hours per month)&lt;/li&gt;
&lt;li&gt;You don’t have to worry about benefits (sick leave, parental leave etc)&lt;/li&gt;
&lt;li&gt;None of the other overhead costs that employees have (e.g. desk, computer, chair, office space)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And in terms of efficiency and bang for buck, agencies can often smash out more high quality work in a couple of months than a single experienced employee could do in 10 months.&lt;/p&gt;
&lt;h2 id=&quot;agencies-have-a-wider-range-of-skills-%F0%9F%91%A8%E2%80%8D%F0%9F%91%A9%E2%80%8D%F0%9F%91%A6%E2%80%8D%F0%9F%91%A6&quot;&gt;Agencies have a wider range of skills 👨‍👩‍👦‍👦&lt;/h2&gt;
&lt;p&gt;Agencies usually have diverse skill sets as compared to employees.&lt;/p&gt;
&lt;p&gt;Whilst everyone loves to think they have T-shaped skills (deep expertise in one area, and broad capabilities across many other areas), the truth is many employees are pretty I-shaped - meaning they just do one thing.&lt;/p&gt;
&lt;p&gt;When you work with an agency, you have access to a team of professionals with different skills and specialties.&lt;/p&gt;
&lt;p&gt;For example, one internal software developer may know backend development and maintain internal systems for a business. However, an agency could offer full-stack development, data warehousing experience, along with AI and ML experience.&lt;/p&gt;
&lt;p&gt;This can be helpful when a business wants to get a specific project done quickly or wants to tap into new markets.&lt;/p&gt;
&lt;h2 id=&quot;agencies-can-automate-manual-processes-%F0%9F%9B%A0&quot;&gt;Agencies can automate manual processes &lt;strong&gt;🛠&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;An economic downturn makes businesses think about where their money is going - and complicated manual processes or tedious human-dependant workflows are an ongoing cost.&lt;/p&gt;
&lt;p&gt;In addition to providing cost savings and a wider range of skills, agencies can help businesses automate processes that would have previously needed human interaction. This is especially relevant if employees are a large cost to the business.&lt;/p&gt;
&lt;p&gt;Internal tasks such as scheduling, data entry, and customer service can be automated with the help of custom software, potentially saving the business a lot of money.&lt;/p&gt;
&lt;h2 id=&quot;bonus-smart-people-are-available-for-hire-%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB&quot;&gt;&lt;strong&gt;Bonus: smart people are available for hire 👩‍💻&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;For agencies, finding great talent is one of the biggest issues, and in a recession there are often more people looking for work. Salaries may be cheaper, and the competition not be so fierce.&lt;/p&gt;
&lt;p&gt;You obviously need to make the call about whether hiring now is a good decision for your agency, but if it is - it could be a good time to do it.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;So even though the economy might be suffering a blow, your service business doesn’t have to.&lt;/p&gt;
&lt;p&gt;Keep your sales and marketing going, make sure your existing client relationships are strong, and focus on doing what you do best - making awesome things.&lt;/p&gt;
</content:encoded></item><item><title>Interview with Steve Thomas of Coding Labs</title><link>https://www.devtoagency.com/interview-with-steve-thomas-of-coding-labs/</link><guid isPermaLink="false">62bba29b3fdc7000013d3ac4</guid><pubDate>Wed, 29 Jun 2022 01:13:32 GMT</pubDate><description>Steve Thomas is a software developer and the founder of Coding Labs [https://codinglabs.com.au] - a development agency based in Queensland Australia. I spoke with Steve [https://twitter.com/steve_coding] recently about his business (which has been running for 17 years!) and I discovered Coding Labs and my previous agency share some key similarities: 1. Initially focused on startup businesses 2. Then moved into building custom software for established businesses 3. Embraces Laravel [https://</description><content:encoded>&lt;p&gt;Steve Thomas is a software developer and the founder of &lt;a href=&quot;https://codinglabs.com.au/?ref=devtoagency.com&quot;&gt;Coding Labs&lt;/a&gt; - a development agency based in Queensland Australia.&lt;/p&gt;
&lt;p&gt;I spoke with &lt;a href=&quot;https://twitter.com/steve_coding?ref=devtoagency.com&quot;&gt;Steve&lt;/a&gt; recently about his business (which has been running for 17 years!) and I discovered Coding Labs and my previous agency share some key similarities:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Initially focused on startup businesses&lt;/li&gt;
&lt;li&gt;Then moved into building custom software for established businesses&lt;/li&gt;
&lt;li&gt;Embraces &lt;a href=&quot;https://laravel.com/?ref=devtoagency.com&quot;&gt;Laravel&lt;/a&gt;, and the Laravel eco-system&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Anyway, that’s enough of an intro, I’ll let Steve tell his own story…&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/06/steve-circle.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;hr&gt;
&lt;h2 id=&quot;can-you-introduce-yourself-coding-labs-to-the-dev-to-agency-readers&quot;&gt;Can you introduce yourself &amp;amp; Coding Labs to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;Hey, I&amp;#39;m Steve Thomas, a software developer, headbanging enthusiast and father to two wild, energetic young boys. The family and I are based on the Gold Coast, Australia.&lt;/p&gt;
&lt;p&gt;I have been using computers since multi-colour monitors were a big deal, and coding real world projects since I was a teenager.&lt;/p&gt;
&lt;p&gt;My agency, Coding Labs, has been around since 2005, and specialises in custom software development with a great fondness for all things Laravel - especially the VILT stack (Vue, Inertia, Laravel, and Tailwind), and the TALL stack (Tailwind, Alpine.js, Laravel, and Livewire).&lt;/p&gt;
&lt;h2 id=&quot;how-did-coding-labs-start&quot;&gt;How did Coding Labs start?&lt;/h2&gt;
&lt;p&gt;Coding Labs was established while I was completing a Diploma of Multimedia, as a way for me to charge for part-time IT work without needing to take up formal employment (ie. have a Boss).&lt;/p&gt;
&lt;p&gt;I was very fortunate that I landed a role in a local business where I was able to not only learn about eCommerce first-hand, but to also get paid to continue teaching myself the craft of software development.&lt;/p&gt;
&lt;p&gt;I was pretty useless at photography and listing items on eBay, but I was (barely) ok at programming and was able to get to work developing a marketplace web app for the client that has survived and thrived for 17 years and counting.&lt;/p&gt;
&lt;h2 id=&quot;do-you-have-a-niche-or-an-ideal-customer-type&quot;&gt;Do you have a niche or an ideal customer type?&lt;/h2&gt;
&lt;p&gt;Our niche is custom software development. The way I think of custom software development is the creation of any software that cannot be purchased off the shelf (or there is a logical motivation to build from scratch).&lt;/p&gt;
&lt;p&gt;Previously many of our clients have been startup-orientated, but our focus nowadays is for the majority of our effort going toward large stable businesses with proven revenue models and long-term opportunities.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;I would say almost all clients have either been referred to us, or found us organically via Google”&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;how-did-you-find-your-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;How did you find your first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;I found the very first client when I went to speak with the Careers Counsellor while I was studying, and she matched me with the aforementioned eCommerce business, who had advertised on the job board.&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve never done paid advertising.&lt;/p&gt;
&lt;p&gt;I would say almost all clients have either been referred to us, or found us organically via Google.&lt;/p&gt;
&lt;h2 id=&quot;what-challenges-did-you-face-early-on-and-how-did-you-overcome-them&quot;&gt;What challenges did you face early on, and how did you overcome them?&lt;/h2&gt;
&lt;p&gt;I did not work with many other developers in the early years, and so had to figure out a lot of things on my own. Back in the late 2000s, there were vastly less free online resources, and where I live on the Gold Coast the software development community was / is pretty tiny.&lt;/p&gt;
&lt;p&gt;Not to mention I was also very introverted.&lt;/p&gt;
&lt;p&gt;To counter this, I got involved in any meetup or co-working space that I could find, went to conferences, and cultivated professional relationships. Eventually I got to the point where I had built a great team around me to collaborate with day-to-day, and the right foundations in place to bring in external experts a few times a year.&lt;/p&gt;
&lt;h2 id=&quot;did-you-have-a-clear-vision-of-what-your-business-would-be-when-you-first-started-and-has-that-changed-at-all&quot;&gt;Did you have a clear vision of what your business would be when you first started, and has that changed at all?&lt;/h2&gt;
&lt;p&gt;In my early 20s I had an idea of growing Coding Labs to a ~10 person agency working in a converted warehouse with Porsche&amp;#39;s for the company cars haha... through experience, now I realise that the trajectory and velocity of software development innovation is wild and I can scarcely imagine how the art of coding will change in the coming years.&lt;/p&gt;
&lt;p&gt;In general terms though, I think the vision is still intact - aside from the fleet of Porsche&amp;#39;s, which would be a ridiculous waste of company money!&lt;/p&gt;
&lt;h2 id=&quot;what-challenges-do-you-face-today&quot;&gt;What challenges do you face today?&lt;/h2&gt;
&lt;p&gt;Finding experienced developers is extremely tough. It is pretty simply a case of high demand and low supply.&lt;/p&gt;
&lt;p&gt;Pulling all the right levers at the right time for a project to succeed, especially when the project is highly experimental / startup orientated, is no walk in the park. We&amp;#39;ve done so much work across the business, top-to-bottom, to try and maximise our odds of success, but it is still tough to accept when a project doesn&amp;#39;t succeed.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“The time invested in going all-in on Laravel has paid enormous dividends and the surrounding ecosystem just keeps getting better and better.”&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;what-do-you-think-sets-coding-labs-apart-from-other-agencies&quot;&gt;What do you think sets Coding Labs apart from other agencies?&lt;/h2&gt;
&lt;p&gt;I think we do a good job of providing a supportive environment for up-and-coming developers, and that in turn leads to strong team camaraderie and great client outcomes.&lt;/p&gt;
&lt;p&gt;We also got really lucky in deciding to move to Laravel around v4. The time invested in going all-in on Laravel has paid enormous dividends and the surrounding ecosystem just keeps getting better and better.&lt;/p&gt;
&lt;h2 id=&quot;what-do-you-hope-your-business-looks-like-in-3-years&quot;&gt;What do you hope your business looks like in 3 years?&lt;/h2&gt;
&lt;p&gt;I&amp;#39;d like to see us emerge as one of the top Laravel agencies in Australia.&lt;/p&gt;
&lt;p&gt;As an owner, I want to be able to spend more extensive time with my family travelling abroad (ie. snowboarding in Canada, summer in the Mediterranean), with the knowledge that all parts of the business can function without me, day to day.&lt;/p&gt;
&lt;h2 id=&quot;what-are-3-things-you-would-tell-a-developer-who-is-thinking-of-starting-a-software-agency&quot;&gt;What are 3 things you would tell a developer who is thinking of starting a software agency?&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;From my perspective, the entire industry is really still in its infancy, and whole sectors of the economy have barely progressed past Word and Excel workflows. I think the timing to be an agency owner is as good as ever.  &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;IT wizardry will not outweigh poor/underdeveloped people skills as a business owner. There will be conflict, there will be headaches. Prepare policies and contracts that anticipate problems. Policy response &amp;gt; emotional response.  &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Talk and consult widely with all sorts of people; strategists, marketers, financers, business owners, end-users, IT folk. Having a strong general knowledge about how things work and where you can be most dangerous with your effort is probably the best tool you can utilize to bring value to your clients.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
</content:encoded></item><item><title>Pricing - equity and profit share</title><link>https://www.devtoagency.com/pricing-equity-and-profit-share/</link><guid isPermaLink="false">62afba343fdc7000013d3828</guid><pubDate>Mon, 20 Jun 2022 00:13:47 GMT</pubDate><description>Welcome to the fifth and final article in my pricing series. Previously I’ve discussed Fixed Price, [https://www.devtoagency.com/pricing-fixed-price/] Time and Materials [https://www.devtoagency.com/pricing-time-and-materials/], a Hybrid combination [https://www.devtoagency.com/pricing-hybrid/] of both, and Value based pricing [https://www.devtoagency.com/pricing-value-based]. For this last article, I talk about two mechanisms that, whilst not a pricing method by themselves, usually impact ho</description><content:encoded>&lt;p&gt;Welcome to the fifth and final article in my pricing series. Previously I’ve discussed &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;Fixed Price,&lt;/a&gt; &lt;a href=&quot;https://www.devtoagency.com/pricing-time-and-materials/&quot;&gt;Time and Materials&lt;/a&gt;, a &lt;a href=&quot;https://www.devtoagency.com/pricing-hybrid/&quot;&gt;Hybrid combination&lt;/a&gt; of both, and &lt;a href=&quot;https://www.devtoagency.com/pricing-value-based&quot;&gt;Value based pricing&lt;/a&gt;&lt;strong&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;For this last article, I talk about two mechanisms that, whilst not a pricing method by themselves, usually impact how a project is priced. That is, taking an equity share in a client project, and taking a profit share in a client project.&lt;/p&gt;
&lt;p&gt;When an agency takes equity in a project (shares) or takes a profit share in a project, this generally means that the project is developed at a discounted price (or possibly even for free).&lt;/p&gt;
&lt;p&gt;You as the development partner directly take on some of the risk, because if the project doesn’t meet financial expectations then you may be out of pocket, or may not make the profit you’d hoped.&lt;/p&gt;
&lt;p&gt;However, if the project exceeds expectations - it can be a very lucrative arrangement.&lt;/p&gt;
&lt;h2 id=&quot;what-is-an-equity-share-%F0%9F%A4%94&quot;&gt;What is an equity share? 🤔&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;In investing, what is comfortable is rarely profitable&lt;/em&gt;”&lt;br&gt;- Robert Arnott, Entrepreneur&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;An equity share is where you are given shares in the business. In an agency or freelancer model, this would generally be in return for a discounted development cost.&lt;/p&gt;
&lt;p&gt;For example, a startup developing a “Facebook for Dogs” may offer you 10% equity in their business, if you agree to develop their MVP for a discount of 50%.&lt;/p&gt;
&lt;p&gt;In the above scenario, if it was a $50,000 project, then you would only charge $25,000 and in return, they would give you 10% of the total shares of the business.&lt;/p&gt;
&lt;p&gt;You would only see money from these shares if:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The business distributes dividends&lt;/li&gt;
&lt;li&gt;The business is acquired (sold)&lt;/li&gt;
&lt;li&gt;The business IPOs (goes public)&lt;/li&gt;
&lt;li&gt;You sell your shares to someone else&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;With dividend payments, you are not selling your shares, but the company is choosing to distribute its profit to its shareholders. This is a very common method for founders to pay themselves and get cash out of the business. However it’s important to note that companies can decide to never distribute dividends, and simply reinvest their profits into the company (and founders pay themselves a wage instead).&lt;/p&gt;
&lt;p&gt;This means your equity might not turn into money for a long time (or ever) so it’s a gamble.&lt;/p&gt;
&lt;p&gt;For an equity arrangement you definitely need a contractual agreement in place, and both parties will need lawyers.&lt;/p&gt;
&lt;p&gt;As with any investment, you should also be kept informed about the business performance. You should receive regular updates from the business letting you know how they are tracking compared to their goals, their current financial situation etc.&lt;/p&gt;
&lt;p&gt;So there are certainly some things to think about before taking on an equity share and offering a reduced price for the build.&lt;/p&gt;
&lt;h2 id=&quot;what-is-profit-share-%F0%9F%A7%90&quot;&gt;What is Profit share? 🧐&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Nobody ever lost money taking a profit&lt;/em&gt;”&lt;br&gt;- Bernard Baruch, American financier and statesman&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;For a profit share arrangement, you come to an agreement with your client that you will receive X percent of the business profits for Y number of years (or forever).&lt;/p&gt;
&lt;p&gt;Similar to an equity share, this would generally be in exchange for developing the project at a discounted rate.&lt;/p&gt;
&lt;p&gt;For example, a startup developing a “Twitter for Birds” product may offer you 25% of their profit for the first 5 years if you agree to develop their MVP for a discount of 50%.&lt;/p&gt;
&lt;p&gt;In the above scenario, if it was a $50,000 project, then you would only charge $25,000. And you would then have a legally prepared agreement stating that you are the receiver of 25% percent of all profits the company sees in the next 5 years.&lt;/p&gt;
&lt;p&gt;In one way profit share is similar to an equity share, in that you could receive money if the company realises a profit.&lt;/p&gt;
&lt;p&gt;However, startups often reinvest profit back into the business when they start making money (for running costs or hiring more staff). Or often raise the founders&amp;#39; salaries to make up for the early years of less income - and all this means there may not actually be any &lt;em&gt;profit to share.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The other downside compared to equity is that profit share is usually for a fixed timeframe (e.g. 5 years), and if in that period the business has a liquidity event such as an IPO, you can’t sell your shares because you don’t actually own any.&lt;/p&gt;
&lt;p&gt;Like equity, you definitely need to get a good lawyer to guide you through this process and balance what you want out of the deal with what is on offer.&lt;/p&gt;
&lt;p&gt;You also need to be kept informed about the business&amp;#39;s finances for the length of your profit share, and regularly see the profit and loss statements of the business - keeping an eye on your investment.&lt;/p&gt;
&lt;h2 id=&quot;benefits-of-an-equity-or-profit-share-%F0%9F%91%8D&quot;&gt;Benefits of an equity or profit share 👍&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Possibility of making more money (possibly significantly more) than just developing the project for a set cost&lt;/li&gt;
&lt;li&gt;Could allow you to build a portfolio across many different clients and industries&lt;/li&gt;
&lt;li&gt;The possibility of being more involved in the project as you have an ongoing financial stake&lt;/li&gt;
&lt;li&gt;The possibility of more ongoing work now that you have a financial relationship&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;negatives-of-equity-or-profit-share-%F0%9F%91%8E&quot;&gt;Negatives of equity or profit share 👎&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;You need to thoroughly understand the business plan and the people who will be carrying it out. As you are putting a lot of trust in them meeting expectations.&lt;/li&gt;
&lt;li&gt;If the project does not meet financial expectations, you will never recoup the money that you discounted&lt;/li&gt;
&lt;li&gt;Being “in bed” with your client at this level could put undue stress on the relationship. E.g. you blame lack of sales and marketing as the cause of the financial issues, whilst they blame the technology you developed&lt;/li&gt;
&lt;li&gt;You are gambling cash-in-hand for a future payout. This could potentially cause short-term financial strain (payroll, your own scaling issues etc).&lt;/li&gt;
&lt;li&gt;You are relying on the company actually realising profits, which they may not if they just reinvest in the business, staff, more products, or larger salaries&lt;/li&gt;
&lt;li&gt;With profit share, a liquidity event may not happen soon (or ever), so your money may be tied up for a very long time&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;my-experience-with-equity-and-profit-share-%F0%9F%93%96&quot;&gt;My experience with equity and profit share 📖&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Opportunities are like sunrises. If you wait too long, you miss them&lt;/em&gt;”&lt;br&gt;- William Arthur Ward, Motivational writer&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I was offered profit share quite a bit, especially in the early years when my agency was working on a lot of startup MVPs.&lt;/p&gt;
&lt;p&gt;I understood how it was beneficial to the client, as it was an easy way for them to save valuable money up front and offset their risk. But for me, I’m slightly risk adverse and it seemed too close to gambling for me.&lt;/p&gt;
&lt;p&gt;I was involved in startups before starting my agency. I was a frontend lead for a startup that built an amazing product, went from 5 people to 50 people very fast, and then imploded.&lt;/p&gt;
&lt;p&gt;I then founded my own startup with some friends, worked really hard, went through a prestigious accelerator, and then fizzled out because we could not find product-market-fit before our runway ran out.&lt;/p&gt;
&lt;p&gt;So I know that the real hard work comes after the product is built - when you ask people to open their wallets for you.&lt;/p&gt;
&lt;p&gt;In all the times I was offered profit or equity share, it was from founders who I didn’t know very well. And if you look at these two arrangements as &lt;em&gt;going into business with someone&lt;/em&gt; - then I would never recommend going into a business with someone you don’t know very well.&lt;/p&gt;
&lt;p&gt;For this reason, I kept my client relationships simple and chose not to have my remuneration tied to their possible future profits.&lt;/p&gt;
&lt;p&gt;I certainly wanted them to be profitable and did my best to help with that, but I didn’t do it because I needed that money back. I did it because I believe that’s what running a good agency is all about.&lt;/p&gt;
&lt;p&gt;Having said that, if it was someone I trusted and knew well, or someone I had total faith their project would be a financial success, then I would consider taking on equity or profit share for discounted development.&lt;/p&gt;
&lt;p&gt;Never say never, otherwise you are closing yourself off from many opportunities.&lt;/p&gt;
</content:encoded></item><item><title>Pricing - value based</title><link>https://www.devtoagency.com/pricing-value-based/</link><guid isPermaLink="false">62a83a2d3fdc7000013d362b</guid><pubDate>Tue, 14 Jun 2022 07:41:39 GMT</pubDate><description>Welcome to the fourth article in my pricing series, after Fixed Price, [https://www.devtoagency.com/pricing-fixed-price/] Time and Materials [https://www.devtoagency.com/pricing-time-and-materials/], and a Hybrid combination [https://www.devtoagency.com/pricing-hybrid/] of the both. So the most common formula for pricing a project is 1. You estimate how long it will take for you to complete it 2. Based on the time estimate, you decide how much money you want to complete it Whether it’s</description><content:encoded>&lt;p&gt;Welcome to the fourth article in my pricing series, after &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;Fixed Price,&lt;/a&gt; &lt;a href=&quot;https://www.devtoagency.com/pricing-time-and-materials/&quot;&gt;Time and Materials&lt;/a&gt;, and a &lt;a href=&quot;https://www.devtoagency.com/pricing-hybrid/&quot;&gt;Hybrid combination&lt;/a&gt; of the both.&lt;/p&gt;
&lt;p&gt;So the most common formula for pricing a project is&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You estimate how long it will take for you to complete it&lt;/li&gt;
&lt;li&gt;Based on the time estimate, you decide how much money you want to complete it&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Whether it’s fixed or time and materials - price is still tightly coupled to time.&lt;/p&gt;
&lt;p&gt;But there’s one pricing method that tries to seperate price from time, and that’s value based pricing.&lt;/p&gt;
&lt;h2 id=&quot;what-is-value-based-pricing-%F0%9F%92%B5&quot;&gt;What is value based pricing? 💵&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Price is what you pay. Value is what you get&lt;/em&gt;”&lt;br&gt;- Warren Buffett&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Value based pricing is a pricing method where you charge the client a percent of the &lt;em&gt;estimated profits&lt;/em&gt; (or &lt;em&gt;estimated savings&lt;/em&gt;) they will see from having the project implemented.&lt;/p&gt;
&lt;p&gt;It’s regarded as the best way to decouple time from cost, and to directly map your price to a percentage of what the client hopes they will make (or save).&lt;/p&gt;
&lt;p&gt;After all, the software you develop can be worth a lot more to a business than the hours you put in - so your true value can be worth a lot more than your time.&lt;/p&gt;
&lt;p&gt;For example, if you are building an automated scheduling system for a logistics company, you determine the overall savings they will gain from reducing human involvement, and charge a percentage of the money they will save.&lt;/p&gt;
&lt;p&gt;At a time and materials rate, you may only charge $50,000 for this system.&lt;/p&gt;
&lt;p&gt;But that logistics company could save up to 1 million dollars per year just by automating their scheduling system - and that’s worth significantly more to their bottom line than $50k.&lt;/p&gt;
&lt;p&gt;Charging this way can see drastically different figures.&lt;/p&gt;
&lt;h2 id=&quot;how-do-i-actually-implement-value-base-pricing-%F0%9F%A4%B7%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;How do I actually implement value base pricing? 🤷‍♂️&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;The true method of knowledge is experiment&lt;/em&gt;”&lt;br&gt;- William Blake, Poet&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Two key ingredients:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Knowledge about how the business is performing&lt;/li&gt;
&lt;li&gt;Knowledge about how this project will affect their bottom line&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Use your &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;Project Workshop&lt;/a&gt; to thoroughly understand your clients business, their revenue, their profit, and what the forecast is for the coming years.&lt;/p&gt;
&lt;p&gt;Some clients may be a bit cautious exposing this information, but reassure them it’s in their best interest that you have a clear understanding of how they work. After all, you’re more than just a “dev shop”.&lt;/p&gt;
&lt;p&gt;You then uncover what impact this new project will have on their business.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Will it save them $W per year by automating previous manual human tasks?&lt;/li&gt;
&lt;li&gt;Will it save them $X per year by rebuilding something they currently pay a lot for?&lt;/li&gt;
&lt;li&gt;Will it make them $Y per year by selling more of their existing product?&lt;/li&gt;
&lt;li&gt;Will it make them $Z per year by introducing a whole new product line?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These are all forecasts that their business predicts will be the outcome of going ahead with this project - and they should know this information already - ideally.&lt;/p&gt;
&lt;p&gt;But if they don’t know it at all, then you can help them work it out.&lt;/p&gt;
&lt;p&gt;Once you have uncovered the estimated impact to their financial position, then you can use this data when formulating your price.&lt;/p&gt;
&lt;p&gt;In terms of how to determine your price, the most common method is you charge between 15% to 30% of the clients first year of revenue.&lt;/p&gt;
&lt;p&gt;For example if your client expects to profit by (or save) $200,000 in the first year, you could charge between $30k to $60k for the project.&lt;/p&gt;
&lt;p&gt;This percentage is just a guide, you can adjust it to meet &lt;a href=&quot;https://www.devtoagency.com/think-niche/&quot;&gt;your niche&lt;/a&gt;, and your clients, and the specific project you are bidding for.&lt;/p&gt;
&lt;p&gt;Managing the delivery time of the project still needs to be handled internally, as you certainly need to ensure you’re not making a loss. However it’s not as important as time and materials, and if priced correctly (and the project adds real value to them), you should be making more than a fixed price project.&lt;/p&gt;
&lt;p&gt;When presenting your pitch and also in your proposal, make sure you clearly state to your client that if the project meets their expectations, that your price is only X percent of their first years revenue.&lt;/p&gt;
&lt;p&gt;This is integral, as it draws a line directly between their value and your value, and psychologically makes the projects cost more palatable than one big number not based on their value.&lt;/p&gt;
&lt;h2 id=&quot;benefits-of-value-based-pricing-%F0%9F%91%8D&quot;&gt;Benefits of value based pricing 👍&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The possibility of getting paid more - maybe a lot more - than fixed price or time based pricing&lt;/li&gt;
&lt;li&gt;Lower psychological barrier, as you are showing your client they will make their money back in X years (based on their own forecasts)&lt;/li&gt;
&lt;li&gt;Encourages transparency and real data about financial expectations&lt;/li&gt;
&lt;li&gt;Decouples your value from time, showing your relationship is worth more than an hourly wage&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;negatives-of-value-based-pricing-%F0%9F%91%8E&quot;&gt;Negatives of value based pricing 👎&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Clients may not take well to the pricing model, as it is less common and will need some education from you&lt;/li&gt;
&lt;li&gt;Relies on projections about what &lt;em&gt;may&lt;/em&gt; happen financially. This may not always come to fruition, and could affect the relationship (e.g. client pays you 15% of projects of 2 years, but two years later projections were down 95%)&lt;/li&gt;
&lt;li&gt;Takes more diligence and work up front to look through real data to determine projections&lt;/li&gt;
&lt;li&gt;Not well suited for projects that are harder to forecast profit. E.g. building a website for a new cafe&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;my-experience-with-value-based-pricing-%F0%9F%93%96&quot;&gt;My experience with value based pricing 📖&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;I really wish I had of tried value based pricing, it would make this section better&lt;/em&gt;”&lt;br&gt;- Chris Rickard, Author&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I’m kind of disappointed I never implemented value based pricing in my agency, so I have no validated data here to share I’m afraid.&lt;/p&gt;
&lt;p&gt;I always loved the value based pricing method, and have read a lot of success stories about it. As I’ve mentioned in other articles, I started off with &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;fixed price&lt;/a&gt;, then moved to &lt;a href=&quot;https://www.devtoagency.com/pricing-time-and-materials/&quot;&gt;time and materials&lt;/a&gt; and finally &lt;a href=&quot;https://www.devtoagency.com/pricing-hybrid/&quot;&gt;a hybrid approach&lt;/a&gt;. From there, most of my clients fell into an ongoing retainer model, meaning we didn’t do project pricing that regularly. After that my agency was acquired - so the opportunity to test value based pricing never arose.&lt;/p&gt;
&lt;p&gt;But if you want to learn more, and see whether this is something you want to try out, there is a great series of posts by Jonathan Stark titled &lt;a href=&quot;https://jonathanstark.com/how-i-realized-that-hourly-billing-is-nuts?ref=devtoagency.com&quot;&gt;How I Realised Hourly Billing is Nuts&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Like any pricing method, you need to experiment to see if it works for you, your niche, and your clients. But one thing is for certain, how you price can have a big impact on your profit. So it’s certainly something that’s worth trying out.&lt;/p&gt;
</content:encoded></item><item><title>Pricing - fixed price + T&amp;M hybrid</title><link>https://www.devtoagency.com/pricing-hybrid/</link><guid isPermaLink="false">629f16753fdc7000013d3470</guid><pubDate>Tue, 07 Jun 2022 09:28:20 GMT</pubDate><description>Welcome to the third article in my pricing series, after Fixed Price [https://www.devtoagency.com/pricing-fixed-price/] and Time and Materials [https://www.devtoagency.com/pricing-time-and-materials/]. So I found fixed price to be too ridged, and often the negatives outweighed the positives. Whereas time and materials didn’t fly with larger government and corporate projects, where one single price is nearly always required. In the third iteration of pricing methods, I combine the two - a hybri</description><content:encoded>&lt;p&gt;Welcome to the third article in my pricing series, after &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;Fixed Price&lt;/a&gt; and &lt;a href=&quot;https://www.devtoagency.com/pricing-time-and-materials/&quot;&gt;Time and Materials&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;So I found fixed price to be too ridged, and often the negatives outweighed the positives. Whereas time and materials didn’t fly with larger government and corporate projects, where one single price is nearly always required.&lt;/p&gt;
&lt;p&gt;In the third iteration of pricing methods, I combine the two - a hybrid between fixed price and time and materials.&lt;/p&gt;
&lt;p&gt;Now it’s not revolutionary, but I found by setting the pricing this way, and introducing a few project management techniques, clients could still integrate feedback and the project evolved.&lt;/p&gt;
&lt;p&gt;Best of all managers (or those controlling the cash) are happy because it seems “fixed price” - so it’s a win win.&lt;/p&gt;
&lt;h2 id=&quot;fixed-price-for-initial-scope-with-contingencies&quot;&gt;Fixed price for initial scope (with contingencies)&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;History is about great forces, yes, but also about contingency&lt;/em&gt;” - Margaret MacMillan, Historian&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We all know the benefits of charging a fixed price. You can charge what you want in order to win the work, and you’re guaranteed that amount (unless you royally screw it up). One clear figure is easier sell to a client, especially if you’re bidding for a tender.&lt;/p&gt;
&lt;p&gt;So with this hybrid pricing method, you still do it all the same. Run an in-depth scoping phase (ideally a &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;Project Workshop&lt;/a&gt;), do your thorough estimation as usual, and price it so you feel confident with the figure.&lt;/p&gt;
&lt;p&gt;The difference to classic fixed price, is that two additional contingencies are added to the estimate:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;Technical risk contingency&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is a percentage you add to the estimate to handle unforeseen technical issues. The amount depends on the “riskiness” of the project, e.g. how many external libraries or vendors you need to be dealing with. But on average, I would say somewhere between 10% and 20%.&lt;/p&gt;
&lt;p&gt;There is no need to include this as a line item in your estimate if you don’t want, you can instead build this into the individual development estimates. This is your own internal contingency - so the client doesn’t necessarily need to know the specifics (but if you want to let them know that’s fine).&lt;/p&gt;
&lt;p&gt;You use this technical risk contingency when you need.&lt;/p&gt;
&lt;p&gt;It’s a buffer, so you don’t need to track the time. If it turns out you don’t need it - great. That&amp;#39;s a bonus of fixed price.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. Project enhancement contingency&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is a percentage you add to the estimate to handle “project enhancements” - which is a polite way of avoiding using the term “scope creep” with your client.&lt;/p&gt;
&lt;p&gt;Clients will be clients, and the scope will creep.&lt;/p&gt;
&lt;p&gt;An amazing feedback item can send a feature in a different direction, which isn’t a bad thing. If it makes the project better, it should be embraced. The percentage here is very dependent on the client and the project, but again I would say around 10% to 20%.&lt;/p&gt;
&lt;p&gt;Unlike the technical risk contingency, you should clearly let the client know how much “project enhancement” time you have allotted in your fixed price. It&amp;#39;s important they are aware of this.&lt;/p&gt;
&lt;p&gt;You should also let them know in your proposal how this time works. A fixed number of hours that they can use to add, remove, and improve items that were not in the original scope.&lt;/p&gt;
&lt;p&gt;The important part is that these hours are tracked, and they cannot go over this without increasing their budget.&lt;/p&gt;
&lt;p&gt;For the project enhancements, I found it easier to save all of these to the end, instead of working on them during the sprints to deliver the initial scope.&lt;br&gt;This way all client feedback that is agreed to be out of scope is simply put in the backlog, and completed after the initial scope of work is finished.&lt;/p&gt;
&lt;h2 id=&quot;time-and-materials-for-additional&quot;&gt;Time and Materials for additional&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;The only reason for time is so that everything doesn&amp;#39;t happen at once&lt;/em&gt;” - Albert Einstein&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Everything that is not in the original scope, and doesn’t fit into the project enhancement contingency time allotted - is then charged on a time and materials basis.&lt;/p&gt;
&lt;p&gt;For example, say in a 3 month project you allotted 15% enhancement contingency, equating to 13.5 days. And upon completing the initially agreed scope there were 22 days worth of enhancements in the backlog.&lt;/p&gt;
&lt;p&gt;You client would then either&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Choose 13.5 days worth of features from the backlog to stay within their fixed price&lt;/li&gt;
&lt;li&gt;Pay an additional 8.5 days (at time and materials) to implement all the features&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This is a simple concept, and if you clearly explain up front that this is how you work, then everyone is on the same page from the start.&lt;/p&gt;
&lt;p&gt;Relationships suffer when things change unexpectedly, so it’s about setting expectations.&lt;/p&gt;
&lt;p&gt;I’ve found that when clients know they have a contingency baked in, they are more open to suggestions and ideas which is a good thing. It’s their product - they should be!&lt;/p&gt;
&lt;p&gt;Ultimately it means more items are added into the backlog, they are more proactive with new ideas, and this usually means more ongoing work past the initial scope.&lt;/p&gt;
&lt;h2 id=&quot;allow-exchanging-features&quot;&gt;Allow exchanging features&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Computers were programmed to swap out error-prone, inconsistent human calculation with digital perfection&lt;/em&gt;” - David Autor, Economist&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The reason I like the hybrid approach is that it brings more flexibility into a fixed price arrangement. And something else that can expand on this, is allowing the client to swap features of a similar size.&lt;/p&gt;
&lt;p&gt;For example - If halfway through they have this great idea for &amp;quot;Feature X&amp;quot; but it is too big to fit into the enhancement contingency, they could choose to remove previously scoped &amp;quot;Feature C&amp;quot; and &amp;quot;Feature D&amp;quot; - in order to fit in the new feature.&lt;/p&gt;
&lt;p&gt;If managed incorrectly this could get a bit messy, as your client might end up swapping everything at the last minute. But as long as you set some clear boundaries, this is a great option to reduce some of the rigidity of a fixed price project.&lt;/p&gt;
&lt;p&gt;Some tips if you decide to include this&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;There needs to be a discussion and research done. Not all features can be removed, especially if ground work has been laid&lt;/li&gt;
&lt;li&gt;The client needs to formally request the change at least a week or so before the sprint starts&lt;/li&gt;
&lt;li&gt;I suggest adding additional time to the new item to cover the change overhead (project management, research etc). This can come out of the enhancement contingency.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;p&gt;After trialing the hybrid pricing method a few times with good success - it became our go to for all projects requiring a fixed price.&lt;/p&gt;
&lt;p&gt;I found it reduced a lot of the negatives of both fixed price and time and materials, and more arguably more importantly, encourages a fruitful ongoing client relationship.&lt;/p&gt;
</content:encoded></item><item><title>Pricing - time and materials</title><link>https://www.devtoagency.com/pricing-time-and-materials/</link><guid isPermaLink="false">6296ab48b684b70001dc7942</guid><pubDate>Wed, 01 Jun 2022 00:15:38 GMT</pubDate><description>This is part 2 in the pricing series, part one was about charging a fixed price [https://www.devtoagency.com/pricing-fixed-price/] for client projects. Let's say you charge $125 per hour. Great, that sounds like a fine amount of money, right? And you win a new project you estimate will take 2 months to deliver, at a fixed price. Everything is going well, until you find an unforeseen issue in the 3rd party API you are integrating with. It can’t handle the scale you need - so you have to rebui</description><content:encoded>&lt;p&gt;This is part 2 in the pricing series, part one was about charging a &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;fixed price&lt;/a&gt; for client projects.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s say you charge $125 per hour.&lt;/p&gt;
&lt;p&gt;Great, that sounds like a fine amount of money, right?&lt;/p&gt;
&lt;p&gt;And you win a new project you estimate will take 2 months to deliver, at a &lt;strong&gt;fixed price.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Everything is going well, until you find an unforeseen issue in the 3rd party API you are integrating with. It can’t handle the scale you need - so you have to rebuild it yourself. It’s a really large problem and adds an extra 4 weeks to the project schedule.&lt;/p&gt;
&lt;p&gt;So the project is now a bunch over time, but because you committed to delivering this project at a fixed price, your profit margin has been halved.&lt;/p&gt;
&lt;p&gt;This is not an uncommon scenario.&lt;/p&gt;
&lt;p&gt;Sure, you might have been able to mitigate the risk by doing more detailed research up front, maybe even a prototype, but no matter how diligent you are unforeseen issues occur.&lt;/p&gt;
&lt;p&gt;Now we’ve all heard that prevention is the best medicine, but we can’t prevent all issues in a software project. So how do you not screw yourself over?&lt;/p&gt;
&lt;p&gt;This is one of the reasons people move to a time and materials pricing method.&lt;/p&gt;
&lt;h2 id=&quot;what-is-time-materials-pricing-%F0%9F%92%B5&quot;&gt;What is time &amp;amp; materials pricing? 💵&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Time is money, so I went and bought a rolex&lt;/em&gt;”&lt;br&gt;- Wiz Khalifa, Rapper&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You charge your client for all the time you spend on their project, and pass-on any material costs you incur. By &lt;em&gt;material&lt;/em&gt; costs I mean things like domain registration, or a third party software component you purchase. Your client pays for all of this.&lt;/p&gt;
&lt;p&gt;You might decide to charge per hour, per day, per week, or per month - it doesn’t matter. The point is you charge for your time. All of it.&lt;/p&gt;
&lt;p&gt;Using this pricing method you provide the client with the same detailed scope and estimate, and put in the same amount of effort you would for a &lt;a href=&quot;https://www.devtoagency.com/pricing-fixed-price/&quot;&gt;fixed price project&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;However unlike fixed price, the estimate you provide your client is really more of a &lt;em&gt;ballpark estimate&lt;/em&gt; - not a fixed quote.&lt;/p&gt;
&lt;p&gt;If the project takes ten hours longer, that’s ten additional hours you charge. If it takes ten hours less, that’s ten less hours you charge.&lt;/p&gt;
&lt;p&gt;Software projects &lt;strong&gt;always&lt;/strong&gt; have changes.&lt;/p&gt;
&lt;p&gt;New features, tweaks, misunderstandings etc. It’s not easy building a great product while keeping a great client relationship - especially on a fixed price. Time and materials can help with that.&lt;/p&gt;
&lt;p&gt;Say your client tests a sprint and asks for new feature ABC? No problem, it’s around X hours work, and we can start it in the next sprint. You don’t have to say “no sorry you never mentioned that in the original scope”.&lt;/p&gt;
&lt;p&gt;However it’s important to educate your client about how you work at the start of your relationship. This way they understand that cost is flexible right at the start, and they also understand scope is flexible. And that ultimately this can mean a better outcome.&lt;/p&gt;
&lt;p&gt;The key to staying within your (ballpark) estimate with a time and materials project involves flexibility on both sides.&lt;/p&gt;
&lt;p&gt;Your client needs to be flexible. If a new feature cost more than they expect, they may need to remove or simplify some other features.&lt;/p&gt;
&lt;p&gt;You need to be flexible because things might change… a lot. You need to embrace the agility, and allow your client to make the changes they need (and time and materials allows them).&lt;/p&gt;
&lt;p&gt;And those pesky unforeseen technical issues that crop up? Well they are no longer a huge loss to you like they are with fixed price. Time spent researching and rectifying these issues is all chargeable.&lt;/p&gt;
&lt;p&gt;However it’s still your responsibility to build a technical risk buffer into your estimate just like you would with fixed price. Best case scenario your client saves money by not needing this, and you should communicate that to them. This is another example of the benefit of this pricing model.&lt;/p&gt;
&lt;p&gt;But just because you get paid for any additional hours doesn’t mean you don’t have risk.&lt;/p&gt;
&lt;p&gt;Strong long term client relationships is the key to building a great business - and if your projects go wildly over time then you will never achieve this.&lt;/p&gt;
&lt;h2 id=&quot;benefits-of-charging-time-materials-%F0%9F%91%8D&quot;&gt;Benefits of charging time &amp;amp; materials? 👍&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your profit is based directly on the margin you build into your rate (hourly, daily etc)&lt;/li&gt;
&lt;li&gt;Risk is no longer all on you (as it is with a fixed price project)&lt;/li&gt;
&lt;li&gt;Clients get more flexibility to add, remove, or tweak features&lt;/li&gt;
&lt;li&gt;All additional features and changes are paid for&lt;/li&gt;
&lt;li&gt;You can invoice regularly based on work completed that period&lt;/li&gt;
&lt;li&gt;Easier to spin into an ongoing retainer (see &lt;a href=&quot;https://www.devtoagency.com/recurring-revenue/&quot;&gt;Recurring revenue&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;negatives-of-charging-time-materials-%F0%9F%91%8E&quot;&gt;Negatives of charging time &amp;amp; materials? 👎&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Your reputation is reliant on your estimation skills&lt;/li&gt;
&lt;li&gt;You can’t just throw a made-up number out there - your pricing is more transparent (you should have never have done this anyway though!)&lt;/li&gt;
&lt;li&gt;Some clients demand fixed price, and will not do time and materials (e.g. government)&lt;/li&gt;
&lt;li&gt;If you don’t communicate the project status regularly, you are at risk of giving your client &lt;em&gt;invoice shock&lt;/em&gt; (a larger invoice than they expect)&lt;/li&gt;
&lt;li&gt;If the project goes over time and the client isn’t happy, you risk losing the client&lt;/li&gt;
&lt;li&gt;Increased project management overhead compared to fixed price. Time must be tracked, aggregated, compared to the plan, schedules adjusted etc..&lt;/li&gt;
&lt;li&gt;Even though you are paid for it, a large time overrun on technical issues can be demoralising for you and your team, and costly for the client&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;my-experience-with-time-materials-%F0%9F%93%96&quot;&gt;My experience with time &amp;amp; materials 📖&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Quality is remembered long after price is forgotten&lt;/em&gt;”&lt;br&gt;-  Aldo Gucci, Chairman of Gucci&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Where I eventually found fixed price projects too rigid and not agile enough, I found time and materials provided the flexibility needed for a great project to evolve.&lt;/p&gt;
&lt;p&gt;I no longer had to say “no” to my clients.&lt;/p&gt;
&lt;p&gt;“No we can’t change that as it’s not in the original scope”.&lt;/p&gt;
&lt;p&gt;“No we can’t add in that great new feature suggestion”.&lt;/p&gt;
&lt;p&gt;All that went away with time and materials, and instead the onus was on the client to decide the outcome they wanted.&lt;/p&gt;
&lt;p&gt;If they want it all, they have to pay more. If they need to stay within a budget, then they have to compromise. And they understood that.&lt;/p&gt;
&lt;p&gt;It also allowed my clients to clearly understand how my agency priced. It wasn’t a mystical big number anymore, it was simple, hourly pricing. This meant raising our prices was easier too - as we grew larger and stepped away from competing on price, and towards &lt;a href=&quot;https://www.devtoagency.com/compete-on-quality/&quot;&gt;competing on quality&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;However as my agency grew, we won larger and longer projects - and often in corporate and government sectors.&lt;/p&gt;
&lt;p&gt;Now that’s all great, but the issue is these projects involved a tender process, and the tender response needed to include, you guessed it, a fixed price. And they hold you to it!&lt;/p&gt;
&lt;p&gt;So whilst time and materials worked well for us, as we grew, the larger projects we went after required a fixed price. This seemed like a step backwards, but after some experimentation I found a middle ground approach, a hybrid, that worked really well.&lt;/p&gt;
&lt;p&gt;In the next article I&amp;#39;ll talk about a hybrid approach that worked great for me - mixing fixed price with time and materials.&lt;/p&gt;
</content:encoded></item><item><title>Pricing - fixed price</title><link>https://www.devtoagency.com/pricing-fixed-price/</link><guid isPermaLink="false">628ebc85b684b70001dc77ad</guid><pubDate>Wed, 25 May 2022 23:41:09 GMT</pubDate><description>In a client services business, how you charge can sometimes be more important than what you charge. It’s not uncommon to experiment with various pricing methods, especially when you are first starting out (I know I did). But it’s important to know that each method has it’s own pros and cons, and to find the method that works best for you will take some firsthand experience. My next few articles will be a rundown on various pricing methods, the benefits and negatives, along with insights based</description><content:encoded>&lt;p&gt;In a client services business, &lt;em&gt;how you charge&lt;/em&gt; can sometimes be more important than &lt;em&gt;what you charge&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;It’s not uncommon to experiment with various pricing methods, especially when you are first starting out (I know I did). But it’s important to know that each method has it’s own pros and cons, and to find the method that works best for you will take some firsthand experience.&lt;/p&gt;
&lt;p&gt;My next few articles will be a rundown on various pricing methods, the benefits and negatives, along with insights based on my experience.&lt;/p&gt;
&lt;h2 id=&quot;but-why-does-the-method-of-pricing-matter-%F0%9F%A4%B7%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;But why does the method of pricing matter 🤷‍♀️&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Havin’ money’s not everything, not havin’ it is&lt;/em&gt;”&lt;br&gt;- Kanye West&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Let’s not beat around the bush, money is the reason businesses exist. Even if you’re in this to save the world, or you just love talking to people - you still need the cash required to get shit done and keep your lights on.&lt;/p&gt;
&lt;p&gt;Software development - like building development - doesn’t always go 100% accordingly to plan. And this is where risk creeps in.&lt;/p&gt;
&lt;p&gt;Software projects are inherently risky. There is risk when creating something new, there is risk when working with a new client or a new technology - and there is also risk when working with clients and tech you have used 100 times before.&lt;/p&gt;
&lt;p&gt;The method of pricing you use on a project controls where some of that risk sits.&lt;/p&gt;
&lt;p&gt;Different pricing methods can shift the risk from you to your client, or can share the risk equally.&lt;/p&gt;
&lt;h2 id=&quot;what-is-fixed-price-pricing-%F0%9F%92%B5&quot;&gt;What is fixed price pricing? 💵&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Price is what you pay. Value is what you get&lt;/em&gt;”&lt;br&gt;- Warren Buffett&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;One of the most common methods of pricing a project is fixed price - a single fixed dollar amount your client agrees to pay to you for delivering the project.&lt;/p&gt;
&lt;p&gt;Your client agrees to pay you $X (or only has $X), and after understanding their requirements you agree to deliver the project for that amount.&lt;/p&gt;
&lt;p&gt;The scope is important in fixed price - as you will require a super tight scope of work up front. You need to thoroughly understand the requirements (both functional and non-functional), and I recommend a detailed scoping session be done with your client before providing your fixed estimate (ideally in a paid &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;Project workshop&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;The most common issue I’ve seen with fixed price projects is going over the schedule time. This usually happens from miscommunications and misunderstandings (lost in translation) - and sometimes technical issues (often when integrating with tech that is not in your complete control, e.g. 3rd party libraries, frameworks, or services)&lt;/p&gt;
&lt;p&gt;I found documenting the project requirements in my own words helped confirm my understanding - even if the client already provided their own written brief. I would reformat the project scope (in &lt;a href=&quot;https://www.devtoagency.com/living-user-story-documentation/&quot;&gt;User Story&lt;/a&gt; format), and then along with my client step through each feature and acceptance criteria, and ensure everyone is exactly on the same page.&lt;/p&gt;
&lt;p&gt;Another common method of risk mitigation for fixed price projects is to add a buffer or safeguard into the pricing, to account for the level of risk involved. This is generally a judgement call based on experience. New technology? Add a buffer. New client? Add a buffer. Unfamiliar industry? Add a buffer.&lt;/p&gt;
&lt;p&gt;From the clients perspective, if you enter into a fixed price deal, then that price is fixed in stone (which is fair enough). So although you &lt;em&gt;can&lt;/em&gt; go back and have an awkward conversation about more money, it’s your responsibility to make sure you’ve put in all the effort required to deliver on the agreed deal.&lt;/p&gt;
&lt;h2 id=&quot;benefits-of-charging-a-fixed-price-%F0%9F%91%8D&quot;&gt;Benefits of charging a fixed price? 👍&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Cost doesn’t have to reflect time. You can charge what it is worth &lt;em&gt;for you&lt;/em&gt; to complete that project at that point in time. Schedule looking empty? You can charge accordingly to make sure you win the work. Schedule looking stupidly full? You could choose to charge a premium to take on this additional work&lt;/li&gt;
&lt;li&gt;Paying a fixed amount for goods &amp;amp; services is a very familiar concept, so this helps with sales&lt;/li&gt;
&lt;li&gt;One clear figure for your client to justify, especially if they are going back to their superiors&lt;/li&gt;
&lt;li&gt;You are guaranteed the price you agree upon (assuming you deliver the work!)&lt;/li&gt;
&lt;li&gt;Client cannot alter the scope of work (at least without altering price)&lt;/li&gt;
&lt;li&gt;Common to get partial payment upfront (e.g. 30% to 50%, or even 100%)&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;negatives-of-charging-a-fixed-price-%F0%9F%91%8E&quot;&gt;Negatives of charging a fixed price? 👎&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Your profit margins are reliant on your estimation skills&lt;/li&gt;
&lt;li&gt;You must pre-emptively build in a risk buffer up-front, and this is often difficult to accurately capture when working with a new client, a new staff member, or a new technology&lt;/li&gt;
&lt;li&gt;Your profit is derived from getting the job done as fast as possible. This encourages an environment of haste, and can be counterintuitive to building strong client relationships&lt;/li&gt;
&lt;li&gt;Time and costs overruns can lead to awkward conversations where you ask for more money (and your client is under zero obligation to give you any). That’s the agreement&lt;/li&gt;
&lt;li&gt;Time and costs overruns can lead to a lack of internal motivation (the project seems endless and worthless)&lt;/li&gt;
&lt;li&gt;It can pit client against vendor. Every small change in scope is a “no”, or a price alteration (which can make for a very transactional relationship)&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;my-experience-with-fixed-price-%F0%9F%93%96&quot;&gt;My experience with fixed price 📖&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Perhaps the reason price is all your customers care about is because you haven’t given them anything else to care about&lt;/em&gt;”&lt;br&gt;- Seth Godin&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;For the first couple of years of running my software agency, I charged fixed price for all projects.&lt;/p&gt;
&lt;p&gt;It was simple, and in the beginning helped get clients over the line. I could charge what I needed to order to get my business off the ground, and sometimes going over an estimate was not a huge deal. A couple of weeks over when we were a small company seemed ok, and I justified it as keeping a good client relationship.&lt;/p&gt;
&lt;p&gt;But as we grew in size, our overheads also grew. More staff, bigger payroll, larger office, more rent. We relied more on our forecasted profit to keep the business afloat, so going a few weeks over on a project with 3 full-time staff became a problem. And it seemed fixed price projects were the problem.&lt;/p&gt;
&lt;p&gt;In retrospect, I don’t really think charging a fixed price was our problem (it was growing pains mixed with internal processes which needed refining). But at the time I believed we had outgrown charging fixed price - and that charging &lt;strong&gt;time and materials&lt;/strong&gt; was to be our saviour.&lt;/p&gt;
&lt;p&gt;In the next article I’ll talk about time and materials pricing method.&lt;/p&gt;
</content:encoded></item><item><title>Recurring revenue</title><link>https://www.devtoagency.com/recurring-revenue/</link><guid isPermaLink="false">6271b758b684b70001dc75d5</guid><pubDate>Tue, 03 May 2022 23:34:16 GMT</pubDate><description>The typical work of software agencies, consultants, and freelancers is project-based. You win the project, provide the service, and receive the agreed payment. But project work can be feast or famine, and a large cause of stress within agencies. Your pipeline can be full, but then some projects get delayed or fall through. You can have zero work scheduled, but then within a week you have triple the amount you can handle. This makes forecasting difficult, and results in very lumpy payment sched</description><content:encoded>&lt;p&gt;The typical work of software agencies, consultants, and freelancers is project-based. You win the project, provide the service, and receive the agreed payment. But project work can be feast or famine, and a large cause of stress within agencies.&lt;/p&gt;
&lt;p&gt;Your pipeline can be full, but then some projects get delayed or fall through. You can have zero work scheduled, but then within a week you have triple the amount you can handle. This makes forecasting difficult, and results in very &lt;em&gt;lumpy&lt;/em&gt; payment schedules.&lt;/p&gt;
&lt;p&gt;Recurring revenue brings reliability to your bank balance and longer-term scheduling. It can help shed the limiting mindset of “project-based work”, and get you (and your client) thinking more of a long term partnership.&lt;/p&gt;
&lt;h2 id=&quot;what-is-recurring-revenue-%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB&quot;&gt;&lt;strong&gt;What is recurring revenue? 👩‍💻&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Recurring revenue is income you receive from a client after recurring time, e.g. monthly. This is different to project payments which generally occur after a certain delivery or milestone is complete.&lt;/p&gt;
&lt;p&gt;Some recurring revenue streams such as retainers and maintenance contracts rely on you completing a set amount of work in a specific period. But others, such as ongoing support, are payments that take place irrespective of whether any support work took place within the period.&lt;/p&gt;
&lt;p&gt;Below I run through some of the more common forms of recurring revenue I implemented within my agency. I also mention a couple of types that may be common, but I never implemented, and why.&lt;/p&gt;
&lt;h2 id=&quot;ongoing-support-%E2%98%8E%EF%B8%8F&quot;&gt;Ongoing &lt;strong&gt;support ☎️&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“Just remember that when nobody was there for you, I was. And when nobody else gave a damn, I did.” - Drake&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Software isn’t as easy as “build it and forget it”. Bugs happen, third-party APIs change, and customers have unexpected urgent requests.&lt;/p&gt;
&lt;p&gt;A ongoing support agreement is a contract between you and your client outlining how you will providing future support services for them.&lt;/p&gt;
&lt;p&gt;You agree to terms such as:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Your availability to support their system in a certain timeframe - e.g. Monday to Friday, 9am to 6pm.&lt;/li&gt;
&lt;li&gt;Your response time and medium for any issues they report - e.g. get back to them within 4 hours after reporting an issue, contact via email.&lt;/li&gt;
&lt;li&gt;Your rectification time, or ideal rectification time - e.g. 24 hours.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The specific variables (timings) depend on two things. What your client requires, and what you are willing to provide. I had support agreements requiring 24 hour support, 365 days per year, with a 15 minute response time. I recommend avoiding that if possible as it&amp;#39;s a big commitment!&lt;/p&gt;
&lt;p&gt;Be clear whether you are supporting the application software, the infrastructure/system, or both. You may be happy supporting all components, but have clear written expectations. If infrastructure is not your thing (and you didn&amp;#39;t set it up), then supporting it may not be in your best interest.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why would a client pay a recurring fee for ongoing system support?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;An issue with a system is never good news for a client. It could mean loss of income or customers, as their business may not be functioning. A support agreement provides the client with confidence that you have the time to help them.&lt;/p&gt;
&lt;p&gt;They pay for you to be available to them at the time they need. Like car insurance, they most likely won&amp;#39;t need it, but if they do you will be there. So it&amp;#39;s money well spent.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why would you offer system support?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;As your business and client base grow, it’s hard to drop everything when something goes wrong. You don&amp;#39;t want to delay current projects trying to fit in these unexpected fixes. Pre-booking time in your schedule allows you to handle these events. If it doesn&amp;#39;t get used for support that&amp;#39;s fine too. But it allows you to have padding if issues do arise... which they can.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What happens if the client has no support issues that month?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;That’s great for them! But like insurance, they still pay the monthly support fee. This is hard for some clients and they may not want to do it. Or they may ask for the support time to roll over to the next month. But like insurance that doesn’t work. With integral systems that need high availability, ongoing support agreements benefit everyone.&lt;/p&gt;
&lt;p&gt;Clients may ask to use the pre-paid hours for new feature development or improvements. I would not recommend this, as in its very nature support is for supporting existing features. It’s up to you (I have done this in the past), but it muddy’s the water if support hours get used for anything other than support.&lt;/p&gt;
&lt;p&gt;Retainers are a better method for new feature work, which I discuss later on.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What happens if the client has too many support issues that month?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s up to you. Your client has agreed to &amp;quot;buy&amp;quot; X hours per month. If your clients wants more hours and you have the capacity - then charge for that work. But if you are too busy, you are under no obligation to do more.&lt;/p&gt;
&lt;h2 id=&quot;system-maintenance-%F0%9F%9B%A0&quot;&gt;&lt;strong&gt;System Maintenance 🛠&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“Intellectuals solve problems, geniuses prevent them” - Albert Einstein&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Often bundled together, it is important to distinguish between support and maintenance. Support is reacting to an event, maintenance is mitigation against an event from occurring.&lt;/p&gt;
&lt;p&gt;Some examples include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ensuring all frameworks and libraries have critical security fixes applied&lt;/li&gt;
&lt;li&gt;Ensuring the system OS has critical security fixes applied&lt;/li&gt;
&lt;li&gt;Database maintenance including performance monitoring and index application&lt;/li&gt;
&lt;li&gt;Monitoring system performance, disk space etc&lt;/li&gt;
&lt;li&gt;Periodic cleanup of any temporary files or log files&lt;/li&gt;
&lt;li&gt;Updating any components that are near end-of-life&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Be clear if you are maintaining the software, the system (or infrastructure), or both. Being responsible for keeping JS libraries up to date is not the same as keeping the core OS up to date. Make sure it’s clear in your agreement what you are maintaining, and you charge accordingly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why would a client pay a recurring fee for ongoing system maintenance?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Because prevention is the best medicine, and that means someone checking their systems. If not, your clients might only know an issue has arisen when their end users start complaining.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why would you offer system maintenance?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Because you want the systems you build to function great. System maintenance before an issue occurs helps avoid interruptions to your project schedules.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What happens if the client has no maintenance issues?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This shouldn’t be a thing. You will outline in the agreement what maintenance activities and on what timeframe. These are regular checks and confirmations, so they will be ongoing.&lt;/p&gt;
&lt;p&gt;Your client will likely never suggest maintenance activities, it’s up to you. Ensure the software you build is up to date, secure, and adhering to best practices. Even if things change over time.&lt;/p&gt;
&lt;p&gt;As mentioned, support and maintenance are often bundled into one agreement. I recommend you explain the difference to your client, as they may choose not to go ahead with one of them. If they agree to both, make sure you have a separate amount of hours allotted to each.&lt;/p&gt;
&lt;h2 id=&quot;retainers-%F0%9F%94%84&quot;&gt;&lt;strong&gt;Retainers 🔄&lt;/strong&gt;&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;Do what you do so well that they will want to see it again and bring their friends.&lt;/em&gt;” - Walt Disney&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A retainer is you agreeing to “keep your time” per month for a specific client, for a pre-agreed fee. This will have a timeframe such as 12 months. In that period you will be at least doing that many hours of work for that client - which is a win for scheduling.&lt;/p&gt;
&lt;p&gt;Retainers are a sign of strong relationships, and a benefit of retainers is ongoing communication. Even if my agency were only doing a small amount of monthly retainer hours for a client, I found we were talking and planning more than with project work. This enhances collaboration and sharing of ideas, leading to more work in the backlog. A better outcome for all.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why would a client pay a recurring fee for a retainer?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Because they want to ensure you are available when they need it. As you win larger projects or get busier, wait times get longer for clients. Pre-booking recurring time in your schedule benefits everyone.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why would you offer retainers?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Because you want your future pipeline full. Combined with a less lumpy sales cycle, your clients get the work they want when they want it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What happens if the client has no retainer work that month?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;No matter how proactive you and your client are, this will happen. The specifics of this should be in the signed agreement, but the two common options are.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Retainer hours must be used within the calendar month, and unused hours are still paid for. This puts the onus on the client to ensure they have work for you to do in the time they are paying for. Like renting an AirBnB for 1 week per month - if you don’t use it you don’t get your money back.&lt;/li&gt;
&lt;li&gt;Unused hours roll over to the next month. Issues happen, and sometimes your client may want to stop (or slow down) one month and do more work the next. Put a cap on the number of hours allowed to roll over. For example, with 20 retainer hours per month you could allow hours to roll over for 1 month (to 40 hours), but after that they must use them.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;paid-workshops-%F0%9F%93%A2&quot;&gt;&lt;strong&gt;Paid workshops 📢&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;I have written about &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;paid project workshops&lt;/a&gt;, which are self-contained scoping workshops. But there are many valuable types of workshops you can run long-term with your clients.&lt;/p&gt;
&lt;p&gt;For clients who do not commit to a retainer, you can run product planning workshops. You spend a day with them and their stakeholders to augment their future product plans with your technical perspective. Then prepare a report with important notes, caveats, and tech recommendations.&lt;/p&gt;
&lt;p&gt;For those who do not commit to maintenance, you can recommend a security review. Bundled with a workshop to take them through the results, and propose a plan on how to deal with any feedback.&lt;/p&gt;
&lt;p&gt;Thinking about the services you offer, and the services your clients need. You will discover some regular paid workshops you could be running. This may initially be out of your comfort zone, but it benefits everyone. You are adding more value to your clients, and their end users or customers.&lt;/p&gt;
&lt;h2 id=&quot;hosting-revenue-%F0%9F%96%A5&quot;&gt;&lt;strong&gt;Hosting revenue 🖥&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Many software development companies make extra income on the top of website hosting. For example, you host your client&amp;#39;s website on AWS which costs around $11.55 per month, charge $50.00 and you make money. This is another form of recurring revenue. This is separate to support and maintenance of the hosting, it’s reselling hosting at a higher rate.&lt;/p&gt;
&lt;p&gt;I never did this, as I preferred my clients to own their own data. They hosted their projects under their own accounts, and on their own cloud-based infrastructure. I would ask them to register for AWS (or similar) and invite me as a user with full access.&lt;/p&gt;
&lt;p&gt;I educated them why we did this, as I believed it avoided “vendor lock-in” on their end, and built greater trust. I look at it like providing a client with detailed documentation to their software. It is exactly that - their software, their systems, and their data. I liked my clients to stick with me because we did a great job, not because it would be difficult to leave us.&lt;/p&gt;
&lt;h2 id=&quot;licensing-revenue-%F0%9F%93%9D&quot;&gt;&lt;strong&gt;Licensing revenue 📝&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;You might develop a valuable software component, and re-use it across client projects. Charging clients an ongoing licensing fee for its use within their software. This could be anything, as long as it’s valuable for the client, and for you has practical applications for reuse.&lt;/p&gt;
&lt;p&gt;I never went down the licensing path, but I&amp;#39;m not discounting it. As with my comments on hosting, I was cautious of vendor lock in. I didn&amp;#39;t want the hassle of having to sell these licensable components. I wanted my clients to be able to leave my agency if they weren&amp;#39;t happy. And they deserve to take everything with them.&lt;/p&gt;
&lt;p&gt;Yes, I probably left money on the table by never going down the licensing path, but I am ok with that.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Leaving the confines of rigid project work helps grow your business. And doing better long-term work for your clients is a win-win.&lt;/p&gt;
&lt;p&gt;I recommend incorporating some level of recurring revenue early on with your clients. This is not to squeeze extra money out of them, but to show you have value on all sides of a project. Before, during, and after. Make sure they feel the investment is worth the value, and it’s up to you to prove your worth.&lt;/p&gt;
</content:encoded></item><item><title>Interview with Carl Erickson of Atomic Object</title><link>https://www.devtoagency.com/interview-with-carl-erickson-atomic-object/</link><guid isPermaLink="false">62523a61b684b70001dc72fb</guid><pubDate>Fri, 15 Apr 2022 03:33:37 GMT</pubDate><description>At the beginning of starting my software development consultancy I was on the lookout for like-minded companies that shared my values and goals - and one of the first I discovered was Atomic Object [https://atomicobject.com/]. I loved how they positioned themselves, and how they didn't beat around the bush about what they do: build complex software that can create a lot of value, technical excellence, generally 3-18+ month long projects (costing between $50k to 5 million), and even told potent</description><content:encoded>&lt;p&gt;At the beginning of starting my software development consultancy I was on the lookout for like-minded companies that shared my values and goals - and one of the first I discovered was &lt;a href=&quot;https://atomicobject.com/?ref=devtoagency.com&quot;&gt;Atomic Object&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I loved how they positioned themselves, and how they didn&amp;#39;t beat around the bush about what they do: build complex software that can create a lot of value, technical excellence, generally 3-18+ month long projects (costing between $50k to 5 million), and even told potential clients right on their landing page that &amp;quot;Custom software is a big investment&amp;quot;. It was so refreshing compared to a cookie-cutter sales pitch, and I felt I had discovered a company that saw client education as an integral part of the relationship. I then became addicted to reading their blog &lt;a href=&quot;https://greatnotbig.com/?ref=devtoagency.com&quot;&gt;Great not Big&lt;/a&gt; which aims to &amp;quot;help people build a successful small company where people love to work&amp;quot;.&lt;/p&gt;
&lt;p&gt;So without further ado I&amp;#39;m excited to share my interview with Carl Erickson, founder and executive chairman of Atomic Object.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/04/carl-erickson.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;hr&gt;
&lt;h2 id=&quot;can-you-introduce-yourself-atomic-object-to-the-dev-to-agency-readers&quot;&gt;Can you introduce yourself &amp;amp; Atomic Object to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;I’m Carl Erickson, founder and executive chairman of Atomic Object. I live in Grand Rapids, Michigan. My wife of 37 years and I have two kids who have launched successfully into the world, and two Siberian huskies still at home. I studied electrical and computer engineering in college. Ten years of higher education and not a single business, finance, marketing, or even economics course.&lt;/p&gt;
&lt;p&gt;After graduate school I taught computer science at Grand Valley State University for 10 years. While I loved teaching, and still do, by the year 2000 I needed a change in my work and a new challenge. I jumped at the chance to join a dot-com era software startup that a former student was a co-founder in. But I jumped carefully, negotiating a leave-of-absence with my dean. My job with the startup was to recruit and run the engineering team. I knew enough to know that the way we taught software engineering in the academy wasn’t terribly effective for the sorts of problems people solved with software in business. But I’d also never done that kind of work before, so I was motivated to try something new. The lightweight methodologies we call “agile” nowadays were just beginning to be discussed. I read Kent Beck’s first book on Extreme Programming and had an epiphany. By March of 2001 the dean wanted to know whether I was coming back to the university in the fall. I was learning so much with the small team we had assembled - two former students of mine and three interns from the college - that I told him I wasn’t. Walking away from my tenured job as an associate professor for a startup doesn’t seem rational in hindsight, but my wife and I had no debt but a mortgage, significant retirement savings, and her very good job.&lt;/p&gt;
&lt;h2 id=&quot;how-did-atomic-object-start&quot;&gt;How did Atomic Object start?&lt;/h2&gt;
&lt;p&gt;Four months after I resigned from the university the startup failed to close a round of financing and shut down. What seems even crazier in hindsight is that I never even considered talking with the dean about undoing my decision and going back to the university. I loved what I was doing, loved writing code for real, loved the people I was doing it with, loved being part of the neighbourhood business community - I just needed a job of some sort. I was 39 years old.&lt;/p&gt;
&lt;p&gt;I took what we had - five smart people, an exciting and effective new approach to development, the remainder of a lease, and used office furniture - and created something new. We did a 180 degree pivot from the startup, launched a software development consultancy, and started looking for people with problems we could solve. My co-founder gave me confidence that we could solve pretty much any problem in software I could convince someone to trust us with.&lt;/p&gt;
&lt;p&gt;Two months after the sudden collapse of the startup, 9/11 happened. Two months after that, my wife lost her job of 17 years when the commercial furniture business went through a dot-com bubble-bursting depression. When I think about it now, I credit confidence in myself and the team, the stability of our personal financial situation, and a belief that there were plenty of people who needed help with software, for both the decision to create Atomic and the perseverance required to survive the first few years.&lt;/p&gt;
&lt;h2 id=&quot;can-you-remember-how-atomic-object-found-its-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;Can you remember how Atomic Object found its first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;I had taught in the graduate program for 10 years. Most of the students in that program were working full-time and seeking to establish a new career in software development. In early 2001 I had negotiated a deal to lease our conference room to Burke Porter Machinery for use by a team working on a strategic software project. They wanted to be offsite. I had taught object oriented design and programming to several of their staff in the graduate program. I’m guessing they probably also wanted to learn more about our Extreme Programming practices. Cohabitating with their team further built the relationship between us. In October I approached their director of engineering about having Atomic build the client side of their next generation client/server end-of-line roll tester product. Incredibly, he accepted my proposal and we had our first customer.&lt;/p&gt;
&lt;p&gt;I think the lesson of our first customer is a very important one. When you’re starting a consultancy as a developer, your first customer need only be someone who you convince to trust you, personally. As a developer, you have all the skills you need to deliver on your promises. Solving people’s problems well has a way of making them ask you to solve more problems. Pretty soon you have more problems to solve than one person can handle, so you ask a friend to help out. A company is launched.&lt;/p&gt;
&lt;p&gt;Our first project lasted about a year. We continued working with that client for at least another five years, but we also found new clients in the critical first 12 months. One was an improv theater company in the suite next door. They needed a website, so we built a CMS and used it for a dozen or so clients before selling it. Another early customer was an e-commerce company that sold die cast model cars. They found us because I registered Atomic with a Sun Microsystems Java Developers directory. The second major customer we had, after Burke Porter, was a color measurement company in town that I met by networking through the local IEEE group. They were also experimenting with Extreme Programming. To this day I have never been more persistent in making a sale. I called and emailed way more times than I felt comfortable. They turned into another 5+ year client and the source of a lot of good work for us.&lt;/p&gt;
&lt;h2 id=&quot;what-challenges-did-atomic-object-face-in-the-early-years-and-how-did-you-deal-with-them&quot;&gt;What challenges did Atomic Object face in the early years, and how did you deal with them?&lt;/h2&gt;
&lt;p&gt;None of us knew anything about business. 10 years of higher education and 10 years of teaching at university had given me an unconscious but strong belief that there’s a correct way to do things. Having no formal education in business, I had some worries that I wasn’t doing the business things the right way. This seemed like a handicap at the time, but I really enjoyed learning, so I just figured out what I needed to know. I used my confidence and semi-iconoclastic personality to do things that seemed right and effective to me regardless of whether it was the standard approach to business. On the policy front, I wanted to create a company where I’d like to work and where we could help people with our skills. On the business front, I applied my analytical engineering mindset and our knowledge of agile practices to modeling the business and establishing our offering to clients.&lt;/p&gt;
&lt;p&gt;Nine months into Atomic’s existence I was doing all the things: coding, selling, networking, marketing, managing, accounting, paying bills, etc. I didn’t do any of them at the expert level, but I could do everything well enough to get by. Being a smart, curious, generalist is another aspect of my personality that proved very handy to starting Atomic. Those traits remain common ones for most Atoms and have served us very well for 20 years. But everyone has a limit, especially everyone with a house, two dogs, two little kids at home, and hobbies. I asked my wife in March of 2002 if she’d help me pay some bills. She wasn’t working at the time as she tried to figure out her next career move. That simple request kicked off a stream of work that’s grown to five people as she pioneered various roles in the company and hired people into those roles. Having a person I totally trusted handle the accounting, facilities, invoicing, and benefits of Atomic was a huge benefit to all of us. Mary’s still working full-time for the company.&lt;/p&gt;
&lt;h2 id=&quot;has-the-goal-or-vision-of-atomic-object-changed-at-all-over-the-years&quot;&gt;Has the goal or vision of Atomic Object changed at all over the years?&lt;/h2&gt;
&lt;p&gt;What we do hasn’t changed much. We offer high-quality, custom, software product development for organizations in most industries who need software to grow revenue, expand market share, or run their business. How we do it has changed enormously over the years. And we’ve dropped some things we did opportunistically and in low volume in the early years like training and a CMS/hosting service. Our purpose has remained constant, though the language we use to describe it has ranged all over the map.&lt;/p&gt;
&lt;p&gt;Atomic exists to be a source and a force. A source of fulfillment for Atoms, and a force for good for our clients and in our communities. I didn’t use that language from the start, but it nicely captures my motivation for starting the company and why I find Atomic to be deserving of hitting our long-term goal of being a 100 year old company.&lt;/p&gt;
&lt;h2 id=&quot;what-do-you-think-sets-atomic-object-apart-from-other-agencies&quot;&gt;What do you think sets Atomic Object apart from other agencies?&lt;/h2&gt;
&lt;p&gt;Michael Porter describes strategic positioning as the combination of your offering, your target market, your business activities which are distinct or which are done in a distinctive fashion, and the level of integration between those activities.&lt;/p&gt;
&lt;p&gt;Some of our activities which are distinctive include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Operational excellence.(This is more of a theme of interconnected activities.) Everything we do is expected to be done well, with data and analysis supporting decisions, disciplined flexibility, and details that are thought through.&lt;/li&gt;
&lt;li&gt;Sales and scheduling. Sales are done by managing partners who are former makers, in a consultative fashion, relying on our marketing-driven strategy to bring leads in where they can apply our “how can I help?” attitude to sales. Scheduling and composition of teams is done by the same people doing sales, and those managing partners are responsible for the P&amp;amp;L of their office.&lt;/li&gt;
&lt;li&gt;Employee ownership. 45 Atoms of the current 80 hold shares through our Atomic Plan. Non-founder shareholders own 66% of the company.&lt;/li&gt;
&lt;li&gt;Hourly pay. Everyone in the company tracks their time closely and is paid for the hours they work. The data we derive from this is valuable for understanding where we spend time. Mistakes on projects can’t be made up for by extra unpaid work by salaried makers.&lt;/li&gt;
&lt;li&gt;1/n profit sharing. Ten percent of our net profits every quarter are divided between all Atoms in equal shares.&lt;/li&gt;
&lt;li&gt;Generalist makers. Our designers and developers focus on honing their product development skills, not one particular language, tool, domain, or industry.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;what-practices-does-atomic-object-follow-to-ensure-technical-quality&quot;&gt;What practices does Atomic Object follow to ensure technical quality?&lt;/h2&gt;
&lt;p&gt;We started from the very beginning with XP writing automated tests at the unit, then integration, then system level. Our software testing followed the typical path of simple automation, then TDD, then continuous integration. We extended this philosophy of validating our work with usability testing of the product and user research for the feature set once we brought design into our agile process.&lt;/p&gt;
&lt;h2 id=&quot;what-are-some-key-things-you-would-tell-a-developer-who-is-thinking-of-starting-their-own-software-agency&quot;&gt;&lt;/h2&gt;
&lt;p&gt;What are some key things you would tell a developer who is thinking of starting their own software agency?&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Take advantage of your development skills and grow your agency from doing solo contract work. This eliminates the need for much startup capital. Our companies can be bootstrapped, and that’s a wonderful thing.&lt;/li&gt;
&lt;li&gt;Build the company you want to work for, with the people you want to work with.&lt;/li&gt;
&lt;li&gt;Focus on being the best you can possibly be and not growth. Think about growth as a natural consequence of being good and a hard problem to solve.&lt;/li&gt;
&lt;li&gt;Inculcate a relentless dissatisfaction with the status quo into your culture.&lt;/li&gt;
&lt;/ol&gt;
</content:encoded></item><item><title>Ownership of code and intellectual property</title><link>https://www.devtoagency.com/ownership-of-code-and-intellectual-property/</link><guid isPermaLink="false">6238061ab684b70001dc71ed</guid><pubDate>Mon, 21 Mar 2022 05:06:36 GMT</pubDate><description>A reader asked me an interesting question about this topic, so I thought I should write about source code and IP ownership. However first and foremost, I ain’t a lawyer, and these laws can vary from country to country - so please ensure you confirm this yourself and your specific situation. When you first start an agency or freelancing, “who owns what” is not often the first thing on your mind. The main issues you worry about are getting projects, getting shit done, and getting paid. But you w</description><content:encoded>&lt;p&gt;A reader asked me an interesting question about this topic, so I thought I should write about source code and IP ownership. However first and foremost, I ain’t a lawyer, and these laws can vary from country to country - so please ensure you confirm this yourself and your specific situation.&lt;/p&gt;
&lt;p&gt;When you first start an agency or freelancing, “who owns what” is not often the first thing on your mind. The main issues you worry about are getting projects, getting shit done, and getting paid.&lt;/p&gt;
&lt;p&gt;But you will get to a point where the question code of ownership and/or intellectual property ownership comes up, and you’ll learn it’s best to get this stuff sorted first before that question arises.&lt;/p&gt;
&lt;h2 id=&quot;who-owns-the-code-%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB&quot;&gt;Who owns the code? 👩‍💻&lt;/h2&gt;
&lt;p&gt;Generally speaking, if you are hired to complete a project, but there is no contract or agreement in place that specifically states otherwise, then &lt;strong&gt;the author of the code (you), owns the code.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Note: that this only applies to business-to-business relationships, if you have ongoing employment and an employment agreement in place - then your employer owns the code.&lt;/p&gt;
&lt;h2 id=&quot;who-owns-the-ip-intellectual-property-%F0%9F%94%90&quot;&gt;Who owns the IP (Intellectual Property)? 🔐&lt;/h2&gt;
&lt;p&gt;Say the work you did has a specific complex component or algorithm that is unique to the software, who owns that? The same rule as the source code. If you are a freelancer or agency, and there is no signed piece of paper that says otherwise, then by default it is you that owns the IP, the author who implemented it.&lt;/p&gt;
&lt;h2 id=&quot;does-everyone-else-know-this-%F0%9F%98%B3&quot;&gt;Does everyone else know this? 😳&lt;/h2&gt;
&lt;p&gt;Nope. Most businesses or individuals that hire someone to code something for them &lt;strong&gt;do not realise this&lt;/strong&gt;, and simply assume that they own the end result (the source code and the IP).&lt;/p&gt;
&lt;h2 id=&quot;what-if-i-don%E2%80%99t-want-to-own-it-%F0%9F%91%8E&quot;&gt;What if I don’t want to own it? 👎&lt;/h2&gt;
&lt;p&gt;Two options:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You can have an initial contract that has a specific clause stating that all code and IP generated belong to the purchaser&lt;/li&gt;
&lt;li&gt;or upon completion of the project, you can have a separate code and IP assignment agreement that both parties sign.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;is-owning-the-code-and-ip-a-good-thing-%F0%9F%A4%B7%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;Is owning the code and IP a good thing? 🤷‍♂️&lt;/h2&gt;
&lt;p&gt;Well, there is two schools of thought here...&lt;/p&gt;
&lt;p&gt;On one hand, if you owned the code and IP you can use parts (or all of it) on other projects without permission, and you could even resell it, or make a SaaS version of the product etc.&lt;/p&gt;
&lt;p&gt;However, this is not a great way to build long-term relationships with your clients, as in my experience the majority of clients would be unhappy with this if they had not explicitly agreed beforehand, and would probably not stick around.&lt;/p&gt;
&lt;p&gt;And whilst legally your arse may be covered, the client services industry is built upon trust, and successful software development agencies and freelancers build their business on ongoing, repeat work from clients - so to summarise, it may not be a great way to make friends.&lt;/p&gt;
&lt;h2 id=&quot;be-transparent-%F0%9F%92%AC&quot;&gt;Be transparent 💬&lt;/h2&gt;
&lt;p&gt;As trust is integral to forming good, ongoing relationships, I found educating clients about the ownership of code and IP was a great way to demonstrate that my agency could be a great partner. A partner that would not only deliver them a great end product, but also a partner that would have their best interests at heart, and that can be relied upon to educate them around parts of the technology industry that they were not aware of.&lt;/p&gt;
&lt;p&gt;On some specific projects where I knew I was bringing a lot of expertise to the table (e.g. I had built some specific component many times before or had a novel way of implementing it), I would ask to retain ownership of part of the project - as I knew this would be great for reuse, and really not that valuable to the client. For example an automated newsletter component with smart customer targeting. Whilst a newsletter company would certainly not want you to own that code and IP,  a financial services business may not really mind if it’s just a very small part of the overall solution you are delivering for them.&lt;/p&gt;
&lt;p&gt;Similarly, if you develop any in-house code, plugins, components etc, and you are leveraging them in a client project, then make it clear in the contract that this is your own code and IP. Even though the law is on your side, be clear with your client that these parts are yours, and whilst they receive the benefit of you using them on their project, it’s common knowledge that you will use it on other projects also.&lt;/p&gt;
&lt;h2 id=&quot;but-what-if-i-do-want-to-reuse-or-resell-%F0%9F%93%A6&quot;&gt;But what if I do want to reuse or resell? 📦&lt;/h2&gt;
&lt;p&gt;That’s totally fine, but just be clear and upfront about it. Navigating these waters will depend on the specific relationship with your client so it’s hard to give concrete advice - but I would say make sure it’s well understood by all parties, it’s written down, and it’s signed.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Discussing source code and intellectual property ownership should really be no different than handling any other topic with your client, do it upfront, be open and trustworthy, and make your client feel comfortable and safe.&lt;/p&gt;
</content:encoded></item><item><title>Living user story documentation</title><link>https://www.devtoagency.com/living-user-story-documentation/</link><guid isPermaLink="false">6222e1f9b684b70001dc702e</guid><pubDate>Sat, 05 Mar 2022 05:05:48 GMT</pubDate><description>I’m not sure if living user story documentation is something anyone else does, but I want to talk about why it evolved in my agency, the benefits we saw, and how we implemented it. ✅Since writing this article I've released Userdoc - and AI-infused requirements management tool to help writing requirements documentation, including User stories, non-functional requirements, user personas, and user journeys. Some caveats: 1. This is pretty specific to client services work, and maybe not so much</description><content:encoded>&lt;p&gt;I’m not sure if living user story documentation is something anyone else does, but I want to talk about why it evolved in my agency, the benefits we saw, and how we implemented it.&lt;/p&gt;
&lt;aside class=&quot;kg-card kg-callout-card kg-callout-card-blue&quot;&gt;&lt;div class=&quot;kg-callout-emoji&quot;&gt;✅&lt;/div&gt;&lt;div class=&quot;kg-callout-text&quot;&gt;Since writing this article I&amp;#39;ve released &lt;a href=&quot;https://userdoc.fyi/?ref=devtoagency.com&quot;&gt;Userdoc&lt;/a&gt; - and AI-infused requirements management tool to help writing requirements documentation, including User stories, non-functional requirements, user personas, and user journeys.&lt;/div&gt;&lt;/aside&gt;
&lt;p&gt;Some caveats:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;This is pretty specific to client services work, and maybe not so much product or SaaS work (but you still may find it beneficial)!&lt;/li&gt;
&lt;li&gt;I know documentation can be controversial, and that the &lt;a href=&quot;https://agilemanifesto.org/?ref=devtoagency.com&quot;&gt;Agile manifesto&lt;/a&gt; implores “&lt;em&gt;Working software over comprehensive documentation&lt;/em&gt;” - but after running a software agency for 8 years, I can confidently say that writing functional documentation (how things behave, not necessarily how they work behind the scenes) contributed greatly to the success of all of our projects, and had a large positive impact on the relationships with our clients.&lt;/li&gt;
&lt;li&gt;I also know that on-going living documentation using user stories is probably controversial also, as the original goal of user stories (in agile-land) is to be a “&lt;em&gt;placeholder for a conversation&lt;/em&gt;”, and not capture all the detail of every requirement etc., but I can only talk about what worked for me.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;quick-overview-of-user-stories-and-friends-%F0%9F%93%9A&quot;&gt;Quick overview of User stories (and friends) 📚&lt;/h2&gt;
&lt;p&gt;Note: Skip this section if you’re familiar with user stories and acceptance criteria.&lt;/p&gt;
&lt;p&gt;One of the best things to come out of agile development is the structured approach to describing a system, and making it a collaborative practise alongside your client and other stakeholders.&lt;/p&gt;
&lt;p&gt;When mapping features of the system with my clients, I start with getting them to identify all the users that interact with the system, e.g.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Car Buyer&lt;/li&gt;
&lt;li&gt;Car Seller&lt;/li&gt;
&lt;li&gt;Site Administrator&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;After that we identity a few specific personas for each of those users, these are fictional characters that will help gain a better understanding of who’s involved (the client generally knows their end users so are best to identify these), e.g.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Persona for Car Buyer&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Name: Jeff Roberts&lt;/li&gt;
&lt;li&gt;Age: 38&lt;/li&gt;
&lt;li&gt;Gender: Male&lt;/li&gt;
&lt;li&gt;Location: Melbourne, Australia&lt;/li&gt;
&lt;li&gt;Work: Accountant&lt;/li&gt;
&lt;li&gt;Motivations / Fears / Frustrations etc.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We then create user stories which represent the high level features of the system. In my agency, user stories formed the basis of our system scoping. User stories are written in the format of “As a &amp;lt;user&amp;gt;, I want &amp;lt;goal&amp;gt; So &amp;lt;reason&amp;gt;, e.g.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;As a Car Seller,&lt;br&gt;I want to signup to create an account with CarFinders,&lt;br&gt;So I can browse and search for&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Whilst a user story is a high level intro, the acceptance criteria for each user story actually are where yourself and your client agree what needs to be implemented&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The signup form has the fields name, email, password, confirm password etc&lt;/li&gt;
&lt;li&gt;Name must be less than 256 characters&lt;/li&gt;
&lt;li&gt;Password and confirm password must be the same value etc..&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you’ve never worked with these before there is heaps more info out there on the net, and it’s a good framework of collaboratively capturing the scope of the project.&lt;/p&gt;
&lt;h2 id=&quot;how-i-used-to-leverage-user-stories-%F0%9F%93%95&quot;&gt;How I used to leverage User stories 📕&lt;/h2&gt;
&lt;p&gt;In a &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;project workshop&lt;/a&gt; I would pop open a new Google doc, and work with the client to identify the users involved in the system. We’d then create a couple of personas for each user, and then start to capture the user stories for each user. We would then breakdown the user stories into high level acceptance criteria. That would be the initial step, and after the project workshop I would review what we captured, ask the client a further bunch of questions, and usually update/finesse acceptance criteria based on those responses.&lt;/p&gt;
&lt;p&gt;At this point, with the user stories and the other outcomes of the &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;project workshop&lt;/a&gt;, I had enough data for a high level project estimate, which I would bundle in with detailed project proposal and send off to the client.&lt;/p&gt;
&lt;p&gt;Assuming the client then chose my agency for the project, when it was nearing the scheduled start date I would pull up the Google doc with the user stories, create a project in JIRA, then create tasks (of type “Story”) for each user story previously identified. I would copy the user story and acceptance criteria into the “description” of the task, and put all the tasks in the backlog (we’d also make some non-functional tasks here such as server setup, deployment setup, security testing etc). I would then work with the client to identify what sprint 1 should look like, and when then go over each task again and confirm/refine the acceptance criteria. This would repeat for each sprint.&lt;/p&gt;
&lt;p&gt;Development would kickoff, and the tasks would be assigned to developers for each sprint.&lt;/p&gt;
&lt;p&gt;As with all software projects, when the client started seeing they project materialise they would add a few features (or a lot of features!), and some changes - no worries, these were created as new tasks in the backlog. Comments where left on the JIRA tasks to help with testing notes, or client feedback, but we didn’t bother changing the user stories in the original Google doc, we just kept it all in JIRA as that turned into the source of truth when we copied the user stories over.&lt;/p&gt;
&lt;p&gt;Let’s assume the worlds a perfect place, and after 4 months of hard work the project was delivered on time, on budget, and just as the client expected. Nailed it.&lt;/p&gt;
&lt;h2 id=&quot;where-the-cracks-start-to-form-%F0%9F%98%AC&quot;&gt;Where the cracks start to form 😬&lt;/h2&gt;
&lt;p&gt;The project was a success, and a few months after go-live the client had some more cash, and a huge list of new features and changes they wanted to implement. Awesome, recurring business is exactly what we want as a software agency.&lt;/p&gt;
&lt;p&gt;Now right away I know that those initial user stories that were written many months ago are stale, because as soon as new tasks where added directly in JIRA and no longer in the initial Google doc, then things became out-of-sync. Similarly those old JIRA tasks with the comments will not be all re-read and referenced, as once a Sprint is set to “finished” who knows where those tasks go 🙂 But that’s not the end of the world, as the initial user stories are not really &lt;em&gt;documentation&lt;/em&gt; so-to-speak, they were more a temporary tool to get a job done. And that’s fine, we can simply create a new Google doc, and create new user stories for the new features.&lt;/p&gt;
&lt;p&gt;What does become a bit tricky is describing changes to existing user stories (that were already implemented) is a little more annoying as we don’t have the source of truth anymore, but we will do our best, maybe something like “As a User, I want to see a new CAPTCHA field on signup, So I can prove i’m not a robot”.&lt;/p&gt;
&lt;p&gt;Because you build amazing software, your client’s customers are happy, your keeps coming back - great work. Maybe they even commit to an ongoing retainer, where you’re making updates to their system every month or so. A gold mine for a service business.&lt;/p&gt;
&lt;p&gt;But as the system grows and grows, at some point you realise there are so many features and nuances to the system, that it’s just too big for a single person to keep it all in their head. Both your team and the clients team start to forget about adverse effects a change may have, and bugs start to slip in more and more (e.g. no one remembered that changing the foobar widget would affect the automated nightly email job). And while a full automated test suite can help with these types of errors, not understanding a system still affects things like estimates (e.g. we thought it was a day in sprint planning, but unfortunately no one remembered X,Y,Z and now its more like a week).&lt;/p&gt;
&lt;p&gt;Your developers also need to work across multiple projects, so unfortunately the ones that worked on the last sprint are not always available to work on the next sprint. This is common, but on a complex system it can lead to unnecessary bugs (e.g. Michael was unaware that 3 sprints ago we introduced user customisable currencies, so whilst fixing a bug in the payment reminder email, he actually introduced another one, as he assumed it was still all in US dollars).&lt;/p&gt;
&lt;p&gt;You get the point, more bugs, quality slips, developers find it harder working on the system. But let’s say because you still do great work, and the client is still happy - and sticks with you for many years.&lt;/p&gt;
&lt;p&gt;For the first 4 years of my agency, that was what it looked like.&lt;/p&gt;
&lt;p&gt;We made people happy, and the better we got as a business, the larger projects we won. And the larger, longer running projects we won, the more projects we would have to run in parallel. The more parallel projects, the more developers moved around, the more knowledge got lost, the more user stories grew stale. Some developers became so integral due to the knowledge they had accrued, that the thought of them leaving could keep my up at night. I knew this was a red flag, and something I had always wanted to avoid - as previously as a programmer I HATED the feeling of being trapped on a project. Good devs leave good jobs for reasons like that.&lt;/p&gt;
&lt;h2 id=&quot;what%E2%80%99s-wrong-with-comprehensive-documentation-%F0%9F%93%9C&quot;&gt;What’s wrong with comprehensive documentation? 📜&lt;/h2&gt;
&lt;p&gt;Whilst I was never an agile purist, I knew that “&lt;em&gt;comprehensive documentation”&lt;/em&gt; was deemed bad, a way of the past, and stank of that term that should not be mentioned… &lt;em&gt;waterfall development&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;But I think the historical issue with comprehensive documentation is more to do with a 250 page bible of upfront instructions that was put together by an entire floor of people in suits, who never actually work alongside the client to ensure it met their true needs. The documentation problem was convoluted UML diagrams created by architecture astronauts (in those same suits!) and then sent over to the developers on the floor below to implement them verbatim. All that plus that original 250 page bible was stale by 4pm of the first day of development, and then the business analysts were working on other new projects, so no one kept it up to date.&lt;/p&gt;
&lt;p&gt;Stale comprehensive documentation is worse than no documentation at all, because you trust, and it lies to you. It is a gigantic waste of everyone’s time.&lt;/p&gt;
&lt;p&gt;However I believe comprehensive documentation that is &lt;em&gt;living and trustworthy,&lt;/em&gt; and describes the functionality but not how to implement it - can be a fantastic asset.&lt;/p&gt;
&lt;h2 id=&quot;mending-the-cracks-%F0%9F%9B%A0&quot;&gt;Mending the cracks 🛠&lt;/h2&gt;
&lt;p&gt;I had known about living documentation for a long time, and having worked with in previous agile companies was familiar with concepts such as BDD (Behaviour Driven Development), and tools such as &lt;a href=&quot;https://cucumber.io/tools/cucumberstudio/?ref=devtoagency.com&quot;&gt;Cucumber Studio&lt;/a&gt;, which can take your documentation about specific features (written in individual text files a specific syntax called Gherkin), and actually execute these as software tests, We initially tried this on a couple of projects, and whilst we liked parts of it, I found it cumbersome to write in the specific syntax, and clients also found it hard to read and sign-off the requirements. My developers also found it more of barrier to keep updated (which completely defeats the purpose), so after looking for alternatives, we realised there isn’t an off-the-shelf solution that can fix this multi faceted problem.&lt;/p&gt;
&lt;p&gt;So after some trial-and-error, we ultimately came up with a simple(ish) solution that meet our needs well:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Writing the user stories in one central place, including the story and the acceptance criteria (we used Confluence, but any similar wiki should be fine)&lt;/li&gt;
&lt;li&gt;Each user story has it’s own unique URL, so you can easily link back to the feature (and never copy-and-paste its contents)&lt;/li&gt;
&lt;li&gt;Version control, so you can always peek back in time to see the evolution of a story or acceptance criteria&lt;/li&gt;
&lt;li&gt;Revising the stories in one central place as changes are agreed upon with the client&lt;/li&gt;
&lt;li&gt;Putting a process in place to ensure #4 above&lt;/li&gt;
&lt;li&gt;Be able to clearly show “future state” changes in the user story and acceptance criteria, vs what is currently in production&lt;/li&gt;
&lt;li&gt;Be able to link user stories via acceptance criteria, allowing you to build a web that can be browsed, as opposed to being forced to read each story sequentially.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;So taking you through an example of the improved method leveraging user stories as living documentation...&lt;/p&gt;
&lt;p&gt;In a project workshop I would pop open Confluence and navigate to the projects space I had already setup. As we identify each user story, I would create a new page under the top-level “User Stories” page. (I had a specific user story template I created to help with this). The user story page would have a title (e.g. “Login”), and user story, and then under that the bullet points of acceptance criteria.&lt;/p&gt;
&lt;p&gt;When creating the JIRA task I would &lt;strong&gt;no longer just copy the story contents&lt;/strong&gt;, but simply add the link to the specific user story Confluence page as the description of the JIRA task. Whilst this did add a little overhead to get to the guts of the story from JIRA (adds 1 click), the benefits of centralising the story far outweighed it, and my team and clients got used to it quickly.&lt;/p&gt;
&lt;p&gt;In terms of the technical implementation details, I would add that in the same description field of the task as a bullet point list under a heading called &amp;quot;Technical details&amp;quot;. I would often do the first iteration of the technical notes, and I would run through with my team in the internal sprint kickoff, and usually flesh the technical details out with more information.&lt;/p&gt;
&lt;p&gt;When any changes were required to existing features, &lt;strong&gt;the existing user story was updated&lt;/strong&gt;, and the specific changes were highlighted in a unique colour (our team and clients understood colours in stories and acceptance criteria indicated a change to existing functionality). A new JIRA task would be created for each of those changes but in the description of the task it not only had the URL to the user stories Confluence page, but also the specific colour the change related to. E.g.&lt;/p&gt;
&lt;h3 id=&quot;page-for-user-story-%E2%80%9Csignup%E2%80%9D&quot;&gt;Page for user story “Signup”&lt;/h3&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/03/image-1.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;p&gt;This represents two new changes, a new CAPTCHA field, and a new T&amp;amp;C’s link. There is no meaning to the specific colours, other than each colour will be implemented as a single JIRA task. Using the colours helped us differentiate changes visually, whilst still keeping the entire features as a single story.&lt;/p&gt;
&lt;p&gt;So from this example, two new tasks would be created in JIRA, both had a description that linked to this user stories page, however one also mentioned “see blue highlight” and the other “see green highlight”.&lt;/p&gt;
&lt;p&gt;Similarly, for deleting functionality we would strikethrough with a grey background. E.g.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/03/image-2.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;p&gt;This represents the First name and Last name field are to be removed, and the new Full name field to be added.&lt;/p&gt;
&lt;p&gt;Once the sprint was released, we then cleared all colours and strikethrough from the stories (taking care not to remove any that are actually still in development in an ongoing sprint).&lt;/p&gt;
&lt;p&gt;Another strength that evolved, was linking to other user stories in the acceptance criteria, e.g.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2022/03/image-4.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;p&gt;These are just made up examples, but the blue underlined test represents links to other user stories in the system. It can allow you to create more self contained stories (e.g. Read and Agree to Terms and Conditions) or reuse stories that are shared across many features (e.g. Displays Validations Errors to user).&lt;/p&gt;
&lt;p&gt;Linking turned a user story into a quasi-interactive map of the system, and turned out to be very powerful in keeping user stories maintainable.&lt;/p&gt;
&lt;p&gt;As I mentioned, making sure documentation is kept up to date is the hardest nut to crack, but as soon as we had one central location for a user story it became easier. The process looked like this...&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Client requests changes (via phone, email, JIRA, whatever)&lt;/li&gt;
&lt;li&gt;The exact changes/requirements are confirmed (again via whatever medium, ideally JIRA comments)&lt;/li&gt;
&lt;li&gt;The changes are then written into the existing user story (or stories), and highlighted to emphases changes from existing functionality.&lt;/li&gt;
&lt;li&gt;New JIRA tasks are created for these changes (referencing the link to the User story and the corresponding change colour this task relates to)&lt;/li&gt;
&lt;li&gt;The client is then asked to review these changes - meaning the client needs to re-read each affected user story (which gives them the whole context), and confirm that the new requirements are highlighted&lt;/li&gt;
&lt;li&gt;When the change is confirmed, this becomes the source of truth for everyone involved (though development and testing).&lt;/li&gt;
&lt;li&gt;Once a release is deployed, and changes highlighted in the stories in that release are then unhighlighted (meaning they are now live, and part of the system).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Once the documentation was living (and reliable), we found the same user stories got referenced at many touch points..&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The project workshop - user stories were created&lt;/li&gt;
&lt;li&gt;Refinement before estimation - user stories were tweaked and detail added&lt;/li&gt;
&lt;li&gt;Client confirmation - user stories were sent to them in the proposal&lt;/li&gt;
&lt;li&gt;Client kickoff workshops - all user stories were ran through with the client (again!)&lt;/li&gt;
&lt;li&gt;Internal team kickoff - all user stories were ran through with the developers (would often bring up items to confirm with client)&lt;/li&gt;
&lt;li&gt;Sprint kickoff - sprint users stories were ran through with client and devs&lt;/li&gt;
&lt;li&gt;Development - devs would reference the story to develop against&lt;/li&gt;
&lt;li&gt;Dev testing - devs would manually test the acceptance criteria of other devs features&lt;/li&gt;
&lt;li&gt;Quality Assurance Testing - internal tester would manually test all acceptance criteria&lt;/li&gt;
&lt;li&gt;User acceptance testing - client would be given a UAT document that lists all stories in the sprint, and would manually test all acceptance criteria&lt;/li&gt;
&lt;li&gt;Release notes to client - user stories (and links to the pages) were circulated to client to confirm what had just been released&lt;/li&gt;
&lt;li&gt;System changes and new features - user stories would be updated and confirmed&lt;/li&gt;
&lt;li&gt;Estimates - user stories would be integral for checking possible impacts or affects of the change&lt;/li&gt;
&lt;li&gt;New developers - user stories would be an integral part of them understanding the system&lt;/li&gt;
&lt;li&gt;New Client staff - often clients would give the same user stories to their own staff&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The amount of touch points the information had showed us just how valuable it was, and whilst it takes a small bit of time up front, it payed huge dividends longterm.&lt;/p&gt;
&lt;h2 id=&quot;what-living-user-story-documentation-solved-%F0%9F%8F%85&quot;&gt;What living user story documentation solved 🏅&lt;/h2&gt;
&lt;p&gt;There were definitely times that keeping the user stories and acceptance criteria up to date seemed cumbersome, but the proof was clear, our bug count when down, our developers were happier, and our clients loved it. Other benefits we found&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A new sprint was no longer as risky as it was once was, even if it was many months after the previous release.&lt;/li&gt;
&lt;li&gt;Developers could switch between projects easier, as people no longer had knowledge silo’d in their heads&lt;/li&gt;
&lt;li&gt;Changes to features were now part of the core documentation, meaning context was available at all times&lt;/li&gt;
&lt;li&gt;Clients embraced having access to the living user stories, and often used it as the documentation that they themselves didn’t have&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For some projects that spanned many years, the living user story documentation became such an asset I feel it really strengthened our client relationships. And as a sales piece, it was easy to quickly show potential clients the amount of detail we would put into (and keep) about their projects - it’s like they got a detailed manual for free (our user stories were often integral for the creation of actual manuals for the clients users too).&lt;/p&gt;
&lt;p&gt;Naturally bugs in the user stories themselves can still happen, either misunderstandings or unclear requirements, however we had multiple touch points to catch these, it’s easier to fix than code. If writing functionality in “user story” style isn’t your thing, thats fine. The real learnings here are more around living documentation, and the benefits that can have for your business and your clients business.&lt;/p&gt;
</content:encoded></item><item><title>Compete on quality</title><link>https://www.devtoagency.com/compete-on-quality/</link><guid isPermaLink="false">61b29142993d27000122b492</guid><pubDate>Wed, 13 Oct 2021 06:25:00 GMT</pubDate><description>Competing based on charging less than your competitors can help you get your business off the ground, but in the long term, undercutting using pricing is a race to the bottom, and there is always someone in the world who can run faster than you. Instead of using price, position your business around quality. For a small business building custom software, focusing on &quot;high quality&quot; over &quot;dirt cheap&quot; is generally a better offering, allowing 1. An emphasis on craftsmanship over just &quot;cutting code</description><content:encoded>&lt;p&gt;Competing based on charging less than your competitors can help you get your business off the ground, but in the long term, undercutting using pricing is a race to the bottom, and there is always someone in the world who can run faster than you.&lt;/p&gt;
&lt;p&gt;Instead of using price, position your business around quality. For a small business building custom software, focusing on &amp;quot;high quality&amp;quot; over &amp;quot;dirt cheap&amp;quot; is generally a better offering, allowing&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;An emphasis on craftsmanship over just &amp;quot;cutting code&amp;quot; (I hate that term)&lt;/li&gt;
&lt;li&gt;Stronger client relationships&lt;/li&gt;
&lt;li&gt;A clearer path to becoming a trusted consultant&lt;/li&gt;
&lt;li&gt;Greater chance of repeat business&lt;/li&gt;
&lt;li&gt;A higher hourly/daily/weekly rate&lt;/li&gt;
&lt;li&gt;Meaning more revenue for less effort&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The hard part is that everyone already says they focus on high quality work - even those dirt cheap dev shops. So whilst saying it is still important, you need to go deeper,  you need to make sure you consistently walk-the-walk.&lt;/p&gt;
&lt;h2 id=&quot;quality-as-your-competitive-edge-%F0%9F%A5%8A&quot;&gt;Quality as your competitive edge 🥊&lt;/h2&gt;
&lt;p&gt;When I say high quality, I don&amp;#39;t just mean in engineering, but quality everything.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A seamless sales process - making the potential client feel comfortable, really listened to, and that they are talking to true experts in their field&lt;/li&gt;
&lt;li&gt;A structured delivery process - there should be little to no surprises to the client, meaning you have educated them on how it will work, and they understand what their involvement needs to be and when.&lt;/li&gt;
&lt;li&gt;A trusted partnership - your relationship doesn&amp;#39;t end when the project ends, you have multiple ways of working long term with them to fit whatever they are looking for.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;its-starts-at-the-start-%F0%9F%91%8B&quot;&gt;It&amp;#39;s starts at the start 👋&lt;/h2&gt;
&lt;p&gt;Super professional from the first interaction through to the last - although hopefully the last interaction is many years away.&lt;/p&gt;
&lt;p&gt;Sales is one of the most important chances you&amp;#39;ll get to differentiate yourself from the competition. You want the potential client leaving that first interaction knowing 2 things&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You truely understand the problem they have&lt;/li&gt;
&lt;li&gt;You have high quality standards and processes that return the best results&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;They will hear you talk about benefits of the &lt;a href=&quot;https://www.devtoagency.com/project-workshops/&quot;&gt;project workshops&lt;/a&gt; you&amp;#39;ve designed from years of experience working with clients like them, and they will also want to hear about (or see) some case studies. I always took the chance to address that although my agency was smaller than the 50+ competitors, here&amp;#39;s why I believe &lt;a href=&quot;https://www.devtoagency.com/small-can-be-great/&quot;&gt;small can be great&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The myth around programmers is that they sit in a dark room all day and can&amp;#39;t communicate with other (normal) humans. You need to bust this myth, but I also think it&amp;#39;s important you don&amp;#39;t gloss over the high quality of standards and processes you have in place to deliver their software.&lt;/p&gt;
&lt;p&gt;Many software agencies focus so much on the human side (to prove they are human!) they end up skipping over the impressive work they do behind the scenes to ensure high quality. Make sure your clients know about the behind-the-scenes work you do, e.g.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Store all their sourcecode in a secure best practise distributed version control system&lt;/li&gt;
&lt;li&gt;Architect your code to balance future extendability with speed to market (and you can highlight that this is a spectrum that can be moved to suite their needs, e.g. an MVP)&lt;/li&gt;
&lt;li&gt;Conduct peer code reviews, ensuring multiple developers are across the exact code written. Often involving nuanced conversation about the specific changes to the code, which can then lead to edits of these changes based on the wider teams feedback&lt;/li&gt;
&lt;li&gt;Write automated test cases to not only ensure high quality code at the time of writing, but also act as a regression test suite meaning a long-term investment in quality&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Don&amp;#39;t go overboard, but make sure they understand what you do is a craft, and that you are a collection of craftspeople that put a lot of effort and energy into ensuring a high quality output.&lt;/p&gt;
&lt;h2 id=&quot;high-quality-software-%F0%9F%92%BB&quot;&gt;High quality software 💻&lt;/h2&gt;
&lt;p&gt;High quality software means a lot of things, and a lot of those are invisible. Easily maintainable, refactorable, testable etc (there are &lt;a href=&quot;https://www.goodreads.com/shelf/show/code-quality?ref=devtoagency.com&quot;&gt;many books on this already&lt;/a&gt;), however to your client, the real measure of high quality software is the amount of bugs it has.&lt;/p&gt;
&lt;p&gt;Now there are two types of bugs,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;An implementation bug - meaning something you tried to do wasn&amp;#39;t working as you expected&lt;/li&gt;
&lt;li&gt;An understanding bug - meaning something between the client and you was lost in translation, and what was working as you expected was not working how they expected&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;When dealing with implementation bugs, I think first and foremost it&amp;#39;s integral to set realistic client expectations, and educate your client right upfront that zero bugs is an illusion. Bugs will happen, it&amp;#39;s just a matter of finding them as fast as possible, and it will take their involvement to ensure we  - both us and them - find and squash them before they ever get to the end user.&lt;/p&gt;
&lt;p&gt;But I also feel it&amp;#39;s ultimately up to you to instil within your agency a thorough internal practise for reducing bugs, and letting everyone in your team know the level of quality you are aiming for. Thorough peer code reviews, automated testing, code linting / static analysis, detailed quality assurance testing, and aiding the client to do thorough user acceptance testing - I feel this is a minimum standard to be deemed high quality.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve also had success with what I call &amp;quot;developer testing&amp;quot; - where once a developer has completed a feature on a specific branch, but before their peers do a code review, another developer manually checks out their branch and does a round of quality assurance testing. Sure, this takes more developer time, but it can fix bugs quicker (before the PR is reviewed), and also helps developers learn other parts of the system they didn&amp;#39;t code - which is also great for knowledge sharing.&lt;/p&gt;
&lt;p&gt;The second category of bugs is what I call &amp;quot;understanding bugs&amp;quot;, and these usually take place in the requirements gather phases - but a misunderstanding can take place anywhere in the process.&lt;/p&gt;
&lt;p&gt;From many years running my agency I believe living documentation that is continuously updated from both yourself and the client is a great way to reduce understanding bugs. I know documentation is often frowned upon (it&amp;#39;s not agile!), but it worked really well for me, and my clients often asked for this documentation after the project as they also found it so valuable. I will followup with another whole article about this, as it&amp;#39;s something I feel strongly about.&lt;/p&gt;
&lt;h2 id=&quot;lead-by-example-%F0%9F%93%A2&quot;&gt;Lead by example 📢&lt;/h2&gt;
&lt;p&gt;I personally met with all new leads for that first interaction. This is a benefit of having a small company, but I knew I didn&amp;#39;t want a salesperson in charge of this, as being a highly technical director of the company at that first meeting shows what the business is built upon. If the CEO is that passionate about high quality software, that means something.&lt;/p&gt;
&lt;p&gt;I was often heavily personally involved in the scoping phases for sprints. As I rarely wrote the code, having that hands-on time to help map business requirements into technical features is a great opportunity to show that quality you uphold, and that everything you do as the owner, director, CEO of the business - is of that same high quality. This is both beneficial for your clients and your staff to be reminded of, as high quality comes from the top down.&lt;/p&gt;
</content:encoded></item><item><title>Project workshops</title><link>https://www.devtoagency.com/project-workshops/</link><guid isPermaLink="false">61b29142993d27000122b491</guid><pubDate>Fri, 26 Mar 2021 22:48:52 GMT</pubDate><description>A turning point for my agency was when we introduced a project workshop for all new projects. But before I get into that, let me tell you about the good old days... In the early years I would do anything to impress a potential new client, I was very confident that technically we could hit their project out of the park - we just had to first navigate through this awkward sales dance first. Back then I think my dance was pretty stock standard for a developer turned agency owner, I'd woo the clie</description><content:encoded>&lt;p&gt;A turning point for my agency was when we introduced a project workshop for all new projects. But before I get into that, let me tell you about the good old days...&lt;/p&gt;
&lt;p&gt;In the early years I would do anything to impress a potential new client, I was very confident that technically we could hit their project out of the park - we just had to first navigate through this awkward sales dance first.&lt;/p&gt;
&lt;p&gt;Back then I think my dance was pretty stock standard for a developer turned agency owner, I&amp;#39;d woo the client with examples of fantastic work we had done before, I would enlighten them to how cutting edge we were with our technology stack - and I&amp;#39;d ask lots of questions about the problems they needed help with.&lt;/p&gt;
&lt;p&gt;Hopefully they had some type of written specification (or written anything!) that I could then reference when putting together a time and cost estimate for them (I mean let&amp;#39;s be honest, that&amp;#39;s why they were here), and then I would send it off to them along with a proposal basically saying &amp;quot;&lt;em&gt;I love you, we can be fantastic together, please choose me&lt;/em&gt;&amp;quot;.&lt;/p&gt;
&lt;p&gt;I wasted a lot of time approaching sales like that.&lt;/p&gt;
&lt;p&gt;It was a very small window of time, and ultimately I think we came off looking like one of a hundred agencies in my city... and I think it just gave the client 2 real data points to make a decision.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Did they get a good vibe from me&lt;/li&gt;
&lt;li&gt;Was the cost estimate right for them&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Whilst a lot of sales is based solely on those 2 points, I knew that wasn&amp;#39;t the business I wanted to build. It was the sales I wanted to be doing, and if I was a client, I knew I wouldn&amp;#39;t have been blown away.&lt;/p&gt;
&lt;p&gt;But then a friend mentioned how they run a project workshop at their agency, and right away I knew that was the piece I had been missing.&lt;/p&gt;
&lt;p&gt;A structured workshop that would not only give more time to dance the sales dance, but also allow us to get a lot more in depth with the client, and in turn provide more value. While other agencies would be throwing proposals and large project estimates at them - I would be honest, and say &amp;quot;&lt;em&gt;Software is complex, and business is complex. For the best chance of success for your project I recommend that together we have a day-long workshop where we can really get to the crux of the problem, work together to identify the best technical solution to solve this, and provide us with deep knowledge in order to then provide an accurate estimate.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;And as previously mention, this was a turning point. A very positive turning point, as we increased our lead conversion by around 10% (which is freaking huge).&lt;/p&gt;
&lt;h2 id=&quot;so-whats-a-project-workshop-%F0%9F%A4%94&quot;&gt;So what&amp;#39;s a project workshop? 🤔&lt;/h2&gt;
&lt;p&gt;It&amp;#39;s not new, it&amp;#39;s not ground-breaking, and I certainly didn&amp;#39;t invent it. Others call it a project inception workshop, a roadmapping workshop, my agency called it a Kickoff workshop. The name doesn&amp;#39;t matter, its purpose matters.&lt;/p&gt;
&lt;p&gt;A project workshop is a session where you guide your potential client through a series of conversations around:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Understanding their individual and/or business history (the context)&lt;/li&gt;
&lt;li&gt;Understanding their problem or the software they are looking to build&lt;/li&gt;
&lt;li&gt;Discussing alternatives, showing that perhaps custom software is not always the answer (and that you are not just trying to weasel money out of them)&lt;/li&gt;
&lt;li&gt;Working with them to articulate the requirements in language that is clearly understood by both them and you (or any other technical partner that wins this gig, no vendor lock in here)&lt;/li&gt;
&lt;li&gt;Educating them on building software and what&amp;#39;s involved (trade-offs, how you work)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;It&amp;#39;s structured, there is an agenda, you keep time, and you document everything. They walk out feeling more clear headed and excited about their project than when they walked in, and you have had time, a long time, to show your expertise.&lt;/p&gt;
&lt;h2 id=&quot;what-do-they-get-out-of-it-%E2%9A%96%EF%B8%8F&quot;&gt;What do they get out of it? ⚖️&lt;/h2&gt;
&lt;p&gt;Business problems are complex, software is complex, relationships are complex. Your potential client is looking for an expert. No matter how confident they appear, they want someone who makes them feel safe in this big decision, someone they can trust, and someone that really understands their problems - and can prove they can solve them.&lt;/p&gt;
&lt;p&gt;That&amp;#39;s what they really get out of it - but what they really want out of it is an accurate cost estimate.&lt;/p&gt;
&lt;p&gt;We know that estimation is an art not a science... and a black art at that. A truly good effort and cost breakdown is not easy, and it&amp;#39;s not quick. So the outcome of the workshop for them needs to be;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A detailed breakdown of all the features we identified, in a common language that any technical partner can understand.&lt;/li&gt;
&lt;li&gt;A comprehensive time and cost breakdown based on those identified features, including all &amp;#39;invisible&amp;#39; components of a great software system, including deployment and sever setup, automated testing, etc..&lt;/li&gt;
&lt;li&gt;If applicable - some key high level user interface wireframes outlining the software.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And with that bundle, they can then take it to any software development company in the world, who would then agree that it&amp;#39;s the best software specification they have ever worked with. Although, they would still probably try and sell them their own project workshop ;)&lt;/p&gt;
&lt;h2 id=&quot;length-of-the-workshop-%F0%9F%93%8F&quot;&gt;Length of the workshop 📏&lt;/h2&gt;
&lt;p&gt;The sweet spot is having three separate sized workshops&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Half a day workshop&lt;/strong&gt; for small projects&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full day workshop&lt;/strong&gt; as the standard&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Custom workshop&lt;/strong&gt; for quite large projects or clients with specific needs&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Once you get used to running these you&amp;#39;ll find one day goes fast. The key is staying to the agenda, and knowing how to politely move things along.&lt;/p&gt;
&lt;h2 id=&quot;cost-of-the-workshop-%F0%9F%92%B0&quot;&gt;Cost of the workshop 💰&lt;/h2&gt;
&lt;p&gt;The workshop should definitely not be free. I charged around $1000 for the one day workshop.&lt;/p&gt;
&lt;p&gt;Your pricing should depend on your agency, I think for projects that are in the $50,0000 to $150,000 range - $1000 to $2000 is comparatively small amount to pay for some up front value.&lt;/p&gt;
&lt;p&gt;As my agency got larger projects ($300,000+) a full-day workshop often wasn&amp;#39;t enough, so we split it into two or three days - and charge between $3k and $6k depending on the project.&lt;/p&gt;
&lt;p&gt;There is a magic psychological thing that takes place when a client first opens their wallet and gives you money. The real trust building begins. They still take a leap of faith, but it&amp;#39;s a much smaller leap than the full project build, a much smaller leap for them to mentally justify spending, and a much smaller leap for the opportunity to spend a day with industry experts.&lt;/p&gt;
&lt;p&gt;Charge half as much for the half day workshop, and a multiple of days for the large custom workshop. (The largest workshop I have ever run cost $50,000, which was many sessions with many client stakeholders, scoping an 18 month long project.&lt;/p&gt;
&lt;p&gt;If you want to, feel free to offer a deduction of the workshop cost from the total project cost if they choose you to deliver the project. This can work well at the start, however after a while you may stop this if you end up running many workshops. After all, even though you don&amp;#39;t need to make billions off these workshops - they are taking you away from other responsibilities.&lt;/p&gt;
&lt;h2 id=&quot;who-should-attend-the-workshop-%F0%9F%91%AF%E2%80%8D%E2%99%80%EF%B8%8F&quot;&gt;Who should attend the workshop 👯‍♀️&lt;/h2&gt;
&lt;p&gt;In the workshop you need to,&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Understand and empathise with the problem they need solved&lt;/li&gt;
&lt;li&gt;Pitch your agency - give examples of great similar work you have done in the past, mention how fantastic your development practises are etc.&lt;/li&gt;
&lt;li&gt;Think fast and on-the-spot - this is the time to get deep with problem solving&lt;/li&gt;
&lt;li&gt;Switch between talking technical, business, UI etc. Wear many different hats.&lt;/li&gt;
&lt;li&gt;Be confident giving advice, even if it&amp;#39;s not what they want to hear&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If thats all you, then you can do the workshop by yourself. The one thing I would recommend is you need to document it, so if it&amp;#39;s just you you&amp;#39;ll want a good quality voice recorder setup so your not scribbling notes for 7 hours.&lt;/p&gt;
&lt;p&gt;Otherwise, if other members of your team add benefit and can come in at certain points (or the whole workshop) then that&amp;#39;s fine. I would say don&amp;#39;t have too many people from your team, keep it to 1, 2, or 3. And similarly from their side I would recommend no more than 1,2 or 3 people also. I have done workshops with 10 people, and it&amp;#39;s.... hard. Too many people means A LOT of talking, and time is important here. It should be fast paced but not rushed.&lt;/p&gt;
&lt;p&gt;I think the ideal is you (as the CEO, owner of the business, technologist, and business guy) - and their main project stakeholder. They should know exactly what they want, the reasons for that, and be able to make decisions on the spot. E.g, &amp;quot;Can feature X be delivered after go-live, or is it integral in the MVP?&amp;quot; etc.&lt;/p&gt;
&lt;h2 id=&quot;providing-an-estimate-range-%F0%9F%94%8E&quot;&gt;Providing an estimate range 🔎&lt;/h2&gt;
&lt;p&gt;Your agency may vary, but personally I always provided time and cost estimates. The agile &amp;#39;no estimates&amp;#39; thing may work for well for product development and internal projects - but in client services land they need something concrete to hang their decision off - other than just good vibes.&lt;/p&gt;
&lt;p&gt;Back in the early days of my agency I would throw the big number out there in the initial proposal email, but when my recommendation turned to &amp;quot;let&amp;#39;s spend more time together in a workshop to really figure this thing out with more accuracy&amp;quot; - it allowed me to offer an initial &lt;em&gt;estimate range&lt;/em&gt; - e.g. somewhere around $XYZ and $ABC - and show them the benefit of the workshop is to get some more data points for a more accurate estimate.&lt;/p&gt;
&lt;p&gt;Just for reference I did not quote fixed price estimate. It was made clear that changes will occur, and the price will go up (or down) depending on those changes. But estimates is a whole other article!&lt;/p&gt;
&lt;h2 id=&quot;selling-the-workshop-%F0%9F%93%A2&quot;&gt;Selling the workshop 📢&lt;/h2&gt;
&lt;p&gt;Before I introduced project workshops I would personally spend a couple of days putting together a proposal and a detailed estimated (based on the data I had from calls and meetings), and then would compile it into an email and hope for the best..&lt;/p&gt;
&lt;p&gt;To break the email down to its bare essentials it&amp;#39;s something like:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Please see &lt;em&gt;our proposal attached. Based on our estimation we feel this would cost &amp;lt;estimate /&amp;gt; to deliver, over a period of &amp;lt;months /&amp;gt; months.&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Once I introduced project workshops, it changed the sales flow. First of all I would mention this to all new clients so they understood it&amp;#39;s how we work. I would mention we can give some initial recommendations and ballpark estimate - but for anything more concrete we really need to speed some time getting deeper into the problem and solution.&lt;/p&gt;
&lt;p&gt;The email turned into something more like...&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Please see a summary of our initial recommendations. At a high level, we feel your project may cost around &amp;lt;low estimate /&amp;gt; to &amp;lt;high estimate /&amp;gt; to deliver, over a period of &amp;lt;low time estimate /&amp;gt; to &amp;lt;high time estimate /&amp;gt; months.&lt;/strong&gt;&lt;/em&gt;  &lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;As previously discussed, we offer a structured Project Workshop process to help solidify a more accurate time and cost estimate - but also (often more importantly) get into the finer details of your project, and combined with our software development expertise come up with a detailed plan of attack.&lt;/strong&gt;&lt;/em&gt;  &lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;For your project we recommend the standard 1 day workshop, which costs $&amp;lt;workshop cost /&amp;gt;. Please note this price is deducted from the actual project cost if you choose us as your technical partner.&lt;/strong&gt;&lt;/em&gt;  &lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;After the workshop we can then create a full project proposal going into detail of the features, costs, risks, and delivery phase - and can also provide an accurate time when this could fit into our schedule. An updated estimate will also be provided, which will be a single amount as opposed to a range.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;You then mention the cost of the project workshop (and the size you recommend for them), the benefit plus when you can schedule it in for them. Make the workshop sooner rather than later), and obviously reiterate the benefits of choosing a workshop.&lt;/p&gt;
&lt;p&gt;With this email we would include two attachments&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A summary of our initial recommendations - essentially just a rehash of the information they have told us in our conversations so far, a quick overview of the technology we would use, plus a summary of this emails contents.&lt;/li&gt;
&lt;li&gt;A brochure of the project workshop - detailing the sizes available, the costs, and an agenda of what the workshop will run through&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;running-the-workshop-%F0%9F%8F%83%E2%80%8D%E2%99%82%EF%B8%8F&quot;&gt;Running the workshop 🏃‍♂️&lt;/h2&gt;
&lt;p&gt;The workshop is still a continuation of the sales dance, so keep dancing.&lt;/p&gt;
&lt;p&gt;Before the workshop guests arrive, make sure everything is prepared in advance. Have fresh coffee, tea, and snacks for your guests. Have water in the workshops space, and if you cross over the middle of the day make sure you pre-order some lunch to be delivered (and confirm dietary requirements beforehand). This should be a great experience for your client, and another opportunity to show them you are an expert at this. So from the moment they arrive, make them feel comfortable, and show them you are excited about the workshop and reassure them of the value both parties will get out of it.&lt;/p&gt;
&lt;p&gt;I ran my workshops in a large meeting room with full length whiteboards, many sticky notes for interactivity, and a large screen with a Google slides breakdown of the days agenda. I had a large table so people could sit comfortably and relaxed, and had lots of pens and paper on the table in case it&amp;#39;s needed.&lt;/p&gt;
&lt;p&gt;When everyone has arrived, been offered a beverage, and has been showing where the toilets etc.. you take them through the workshop agenda. Highlight how long each area will go for, and that there will be breaks throughout the day (besides lunch, also have a couple of 15 minute breaks).&lt;/p&gt;
&lt;p&gt;Obviously the actual guts of the workshop is the discussion that you facilitate.&lt;/p&gt;
&lt;p&gt;You should not be talking for the whole time, you need to be asking questions, probing for more information - and making your potential clients do the real &amp;#39;workshopping&amp;#39; for you.&lt;/p&gt;
&lt;p&gt;Tailor the workshop contents on the types of projects your agency handles, the niche you focus on - After 10 or so workshops, I&amp;#39;d created a general agenda that worked for 95% of all clients - and after you implement this you will undoubtedly do the same.&lt;/p&gt;
&lt;h2 id=&quot;example-workshop-agenda-%E2%9C%85&quot;&gt;Example workshop agenda ✅&lt;/h2&gt;
&lt;p&gt;Below is the agenda I used for a 1 day workshop, but as mentioned your own workshop should be developed to suite your specific needs. For example, as I focused on custom software for existing businesses (often internal software), UI and UX was generally not a big component. If you were doing public facing software you would most likely need to spend more time on that area etc.&lt;/p&gt;
&lt;p&gt;The agenda below is high level, but with each section you should teach the workshop guests about what you are running through, and make it known that it is a collaborative workshop. Everyone should get involved, ask questions, add comments. It&amp;#39;s just your job to make sure everything gets done on time.&lt;/p&gt;
&lt;h3 id=&quot;1-welcome-introduction&quot;&gt;1. &lt;strong&gt;Welcome &amp;amp; Introduction&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Welcome&lt;/strong&gt; - Thanks people for coming etc.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agenda&lt;/strong&gt; - Running through the agenda (this) along with rough times&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Outcomes&lt;/strong&gt; - A re-hash of what will come out of today&amp;#39;s workshop, and the deliverables you will provider afterwards (the proposal, a detailed estimate, perhaps wireframes etc).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;2-about-us&quot;&gt;2. About us&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Our Values &amp;amp; Standards&lt;/strong&gt; - A time to (quickly) talk about why your agency is awesome.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Our Team, Processes, &amp;amp; Tools&lt;/strong&gt; - Intro to your team members (I used Google slides for this), and overview of how you work (e.g. Agile), and the tools you use (e.g. JIRA, Figma, whatever)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;3-about-you&quot;&gt;&lt;strong&gt;3. About you&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;How did we get here, and why now?&lt;/strong&gt; - Why is the client here today, what is the history that lead them to this point. You may know some of this, but you can go deeper here.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Goals -&lt;/strong&gt; What are their personal and professional goals related to this project, make sure they are clearly documented. They are important to refer back to.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Success Definitions&lt;/strong&gt; - What does &amp;quot;success&amp;quot; look like for this project? How do we know if we had nailed it?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Current Solutions / Alternatives&lt;/strong&gt; - Is there anything else besides custom software development that could solve this problem? If it&amp;#39;s a product, what alternatives exist right now (and why are you better?)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What Keeps You Up At Night?&lt;/strong&gt; - What is the worst case scenario about embarking on this project? What is the work possible thing that could go wrong?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project Trade-Offs / Priorities (Time vs Scope vs Cost)&lt;/strong&gt; - On time, fully featured, within budget - the triple constraint of the &amp;#39;project management triangle&amp;#39;. They have to pick two, they cannot have all three. Teach them that there are trade-offs in software, and find out their highest priorities.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;4-users&quot;&gt;&lt;strong&gt;4. Users&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;User Types&lt;/strong&gt; - Identify all the users involved in the system. Who will interact with it, what roles are required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User Personas&lt;/strong&gt; - Take each user type and identify a few &lt;a href=&quot;https://xd.adobe.com/ideas/process/user-research/putting-personas-to-work-in-ux-design/?ref=devtoagency.com&quot;&gt;user personas.&lt;/a&gt; This will help you relate more to the actual end users, and can always refer back to personas when thinking of the solution features&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;%E2%80%94-lunch-break-%E2%80%94&quot;&gt;- &lt;strong&gt;Lunch break -&lt;/strong&gt;&lt;/h3&gt;
&lt;h3 id=&quot;5-solution&quot;&gt;&lt;/h3&gt;
&lt;p&gt;5. Solution&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Current Understandings&lt;/strong&gt; - You reiterate back your understanding of what they are looking for / what the solution needs (quick overview)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Feature&lt;/strong&gt; &lt;strong&gt;Breakdown&lt;/strong&gt; - This is the big one. For each user type identified, write down the specific features they can interact with in the system. I recommend using &lt;a href=&quot;https://www.mountaingoatsoftware.com/agile/user-stories?ref=devtoagency.com&quot;&gt;User Stories&lt;/a&gt;, and writing them on sticky notes (on a whiteboard) under each user type identified.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;6-project-phases&quot;&gt;6. Project Phases&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Overview -&lt;/strong&gt; mention how all projects have phases, and even if they do not want to release without &amp;#39;everything&amp;#39; you still break it into phased deliverables for testing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;MVP&lt;/strong&gt; - What could the absolute bare-bones deliverable look like? Would they be willing to release an MVP without first building all the features identified.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Possible phases&lt;/strong&gt; - organise features previously identified into phases. A good rule of thumb is always aim for a minimum of 3 phases, and I always prioritise the most important features in the earlier phases (this makes it easier to cull features if needed).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;7-ui-ux-session&quot;&gt;7. UI &amp;amp; UX Session&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;User Interface Discussion&lt;/strong&gt; - Is there any specific UI inspiration? Or if not, what is the general &amp;#39;mood&amp;#39; we are going for&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;User Experience Discussion&lt;/strong&gt; - Discuss UX, and also make sure to refer back to the identified user personas to make sure you are taking all users into account.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;8-wrap-up&quot;&gt;8. Wrap up&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Overview&lt;/strong&gt; - mention how there was a tonne of information and it will be super valuable in putting together their thorough proposal and estimate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Feedback&lt;/strong&gt; - Always ask what people thought, which parts they found the most valuable etc.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Thanks -&lt;/strong&gt; thank your guests for coming, remind them of the next steps that you will do from here.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When I first ran these with startups I added another section called &amp;quot;Product definition&amp;quot;. It contained things like how they would pitch your service to their clients, their segments and channels they would acquire users, how much it could cost per user etc. The point is your workshops will evolve with you and as you gain more experience.&lt;/p&gt;
&lt;h2 id=&quot;multiple-workshop-offerings-%F0%9F%92%B8&quot;&gt;Multiple workshop offerings 💸&lt;/h2&gt;
&lt;p&gt;The one initial project workshop worked well for my agency, however I know some other agencies that have a series of paid workshops, treating these like a product that users can buy if needed.&lt;/p&gt;
&lt;p&gt;I think the types of workshops you should offer should be around your agencies specific expertise.. Don&amp;#39;t go offering a &amp;#39;Pricing strategy&amp;#39; workshops for startups if you don&amp;#39;t have real, valuable expertise in the area.&lt;/p&gt;
&lt;p&gt;To be honest I never considered other workshop types because my agency was too busy, and I think you need to be careful about offering too many (feeling like you &amp;quot;do everything&amp;quot;) but some other examples of niche paid workshops could include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A dedicated user interface and user experience workshop&lt;/li&gt;
&lt;li&gt;A startup workshop - going deep into the MVP, customer acquisition, pricing etc&lt;/li&gt;
&lt;li&gt;A digital strategy workshop - long term digital strategy planning.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;Workshops are a great way to show your expertise, gain more time with potential client&amp;#39;s (or existing clients) - whilst creating value beyond just &amp;#39;working software&amp;#39;, value that is a key component to a long term partnership.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you enjoyed this article please subscribe to the newsletter below.&lt;/strong&gt;&lt;/p&gt;
</content:encoded></item><item><title>Referrals from friends and family</title><link>https://www.devtoagency.com/referrals-from-friends-and-family/</link><guid isPermaLink="false">61b29142993d27000122b490</guid><pubDate>Wed, 10 Mar 2021 21:17:17 GMT</pubDate><description>Sales. I'll be honest, it's a topic I have been avoiding because its just so BIG. Instead I am going to start with a small chunk of sales - with something that greatly impacted my agency. &gt; &quot;People influence people. Nothing influences people more than a recommendation from a trusted friend. A trusted referral influences people more than the best broadcast message. A trusted referral is the Holy Grail of advertising&quot; ― Mark Zuckerberg A referral is somebody referring your business to somebody el</description><content:encoded>&lt;p&gt;Sales. I&amp;#39;ll be honest, it&amp;#39;s a topic I have been avoiding because its just so BIG. Instead I am going to start with a small chunk of sales - with something that greatly impacted my agency.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;People influence people. Nothing influences people more than a recommendation from a trusted friend. A trusted referral influences people more than the best broadcast message. A trusted referral is the Holy Grail of advertising&amp;quot; ― Mark Zuckerberg&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A referral is somebody referring your business to somebody else. Pretty obvious really, but the impact is huge. People are four times more likely to buy when referred by someone they know (&lt;a href=&quot;http://www.nielsen.com/us/en/insights/news/2013/under-the-influence-consumer-trust-in-advertising.html?ref=devtoagency.com&quot;&gt;study&lt;/a&gt; by Nielsen), so considering this multiplier - referrals need to be a core part of your sales strategy.&lt;/p&gt;
&lt;p&gt;Unfortunately the word-of-mouth sales is not as popular as other methods such as online ads - but I think the reason behind that is that it&amp;#39;s less tangible. It&amp;#39;s easier to throw money into advertisements where you are sure your ad will be shown - but how do you encourage others to recommend your business?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;One customer, well taken care of, could be more valuable than $10,000 worth of advertising&lt;/em&gt;” ― Jim Rohn, Entrepreneur, author and motivational speaker&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;My agencies first 7-figure client was via referral. Specifically an old colleague of mine who was now working at a big boring business, and thankfully that business needed custom software. Obviously our proposal and pitch must have been pretty good - but that &lt;em&gt;warm&lt;/em&gt; lead from someone that both knew and trusted me, I believe that was the force that helped the pendulum swing in my favour.&lt;/p&gt;
&lt;p&gt;When I first started my agency I must be honest I got a little spammy. I sent an email to many friends and family members letting them know I was building custom software (and specifically focusing on startup MVPs at the time), and that if they knew anyone interested it would be great to have an introduction. Then a couple of years later when we pivoted into business automation software, I did the same again. Whilst this email was unsolicited, and I was asking them for a favour, I think ultimately people are happy to connect people if it&amp;#39;s doing everyone a favour. I might be looking for more projects, but they might also know a Plumbing business who is looking for some custom scheduling software - and if they introduce us everyone can win.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m always going to go on about &lt;a href=&quot;https://www.devtoagency.com/think-niche&quot;&gt;having a niche&lt;/a&gt;, and this is no exception, as communicating your value proposition clearly is a lot simpler if you are laser focused. You need to be clear about;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What you do, and what you are an expert in&lt;/li&gt;
&lt;li&gt;What you can do for them&lt;/li&gt;
&lt;li&gt;Some examples of previous successes&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Hopefully your website is super targeted around the service niche you offer, but if your agency is more generally focused it could be beneficial to include a tailored PDF brochure which outlines a specific niche you are targeting. If you are asking friends and family to do you a favour and refer you to potential clients, being clear is key.&lt;/p&gt;
&lt;p&gt;An example email could look like...&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Hi &amp;lt;name /&amp;gt;, hope you are having a great week!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;I was just wondering if I could ask a small favour, my growing software development agency &amp;lt;business-name /&amp;gt; focuses on developing high quality software for &amp;lt;niche /&amp;gt;, and I&amp;#39;m currently looking to generate new business.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The reason for my email is I&amp;#39;m reaching out to some key people I trust to see if you might know any individuals or businesses in your circle that could benefit from our software development services, and could be good for us to talk to.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Areas that we focus on X, Y, and Z, and have worked with existing clients in the industries A, B, and C. We have had great success including &amp;lt;some example of a good outcome&amp;gt;. Some recent examples of our work can be seen at &lt;a href=&quot;http://business-name.com/portfolio?ref=devtoagency.com&quot;&gt;http://business-name.com/portfolio&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you can&amp;#39;t think of anyone that&amp;#39;s totally fine, but if anyone comes to mind it would be fantastic if you could share their contact information and I can introduce myself - or even do an introduction email between them and myself.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;(Optional) I have attached a small PDF of our services that you could email on to anyone you think may be interested.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Thanks in advance,&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&amp;lt;you /&amp;gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Although it is a little spammy - don&amp;#39;t be an actual spammer. Only send this to existing acquaintances you actually know and trust. Examples include&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Friends&lt;/li&gt;
&lt;li&gt;Family&lt;/li&gt;
&lt;li&gt;Old work colleagues&lt;/li&gt;
&lt;li&gt;Old school friends&lt;/li&gt;
&lt;li&gt;You get the picture&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I&amp;#39;ll give you a heads up, this is not going to generate a billion referrals, at least right away. Instead you might get many &amp;quot;I can&amp;#39;t think of anything now but I will keep it in mind!&amp;quot;. And that&amp;#39;s totally fine, because this email serves two integral purposes:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;To get a reply that includes one or more referrals&lt;/li&gt;
&lt;li&gt;To plant a seed in people&amp;#39;s heads&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The seed is important, as you have now asked them directly for the favour, even if they cannot think of anyone today, perhaps when they are at that pool party in 3 week&amp;#39;s time they will think of you when a friends wife is talking about her business needing to &amp;quot;rebuild their accounting system&amp;quot; (or whatever).&lt;/p&gt;
&lt;p&gt;This doesn&amp;#39;t just need to be a once-off exercise. I recommend this is something to do periodically. Don&amp;#39;t just re-send the same email to the same people, but overtime as you meet new people and make more connections - these can be future recipients. If like my experience your business changes its niche focus, then you should re-write and re-target your email, and then you can send again to the same people. As you are now offering a different tailored service, they may be able to think of someone in their circle who could benefit from your new direction.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Free publicity and word of mouth is probably the best and cheapest form of advertising. Learn to use it to your advantage&lt;/em&gt;&amp;quot; ― Richard Branson&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Don&amp;#39;t be afraid to put yourself out there, and don&amp;#39;t be afraid to ask. People trust people.&lt;/p&gt;
&lt;p&gt;My agencies second 7-figure client was also via referral - but that time the referral came from my first 7-figure client.&lt;/p&gt;
&lt;p&gt;Referrals have always played a big role in success.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Hopefully you are sold on the power of referrals, and if you weren&amp;#39;t already, will now think about incorporating this into your practises. If you enjoyed this article please hit the &lt;strong&gt;Subscribe Now&lt;/strong&gt; button below for more insights on how to start and run a software development agency.&lt;/p&gt;
&lt;p&gt;If you have any thoughts, feedback, or questions, feel free to reach out to me on Twitter &lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;&lt;/p&gt;
</content:encoded></item><item><title>My path from developer to agency owner</title><link>https://www.devtoagency.com/my-path-from-developer-to-agency-owner/</link><guid isPermaLink="false">61b29142993d27000122b48f</guid><pubDate>Tue, 02 Mar 2021 21:26:08 GMT</pubDate><description>I'm sure out there somewhere there have been software developers who started their own successful agencies with little to no industry experience, but for me it was definitely a matter of 'stacking the bricks'. Meaning I needed to accrue certain experiences over a number of years to ultimately be confident making the leap of faith into my own business. And I'm glad I did. I'm not solely talking about programming or technical experience here, in fact for me it was the soft business skills I reall</description><content:encoded>&lt;p&gt;I&amp;#39;m sure out there somewhere there have been software developers who started their own successful agencies with little to no industry experience, but for me it was definitely a matter of &amp;#39;stacking the bricks&amp;#39;. Meaning I needed to accrue certain experiences over a number of years to ultimately be confident making the leap of faith into my own business. And I&amp;#39;m glad I did.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not solely talking about programming or technical experience here, in fact for me it was the soft business skills I really needed exposure to. Programming was my passion and hobby, so it was easier for me to up skill as far as that was concerned, however skills such as sales, project management, and nurturing client relationships - these were harder for me to learn on my own.&lt;/p&gt;
&lt;p&gt;My evolution from developer to agency owner went through 3 key periods:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Gaining industry experience by working at an agency&lt;/li&gt;
&lt;li&gt;Gaining business experience by freelancing&lt;/li&gt;
&lt;li&gt;Starting my own agency&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;So far I have written a bunch about starting my agency, but in this piece I want to write about what I learnt from those phases. I&amp;#39;m a big believer that there are many paths to the same destination - so this is by no means a mandatory requirement... but for me these two periods of learning gave me the experience and confidence I needed to build my business, and I believe make my business a success.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;The only place success comes before work is in the dictionary&lt;/em&gt;&amp;quot; ― Vince Lombardi, American football coach&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;experience-gained-by-working-in-an-agency-&quot;&gt;Experience gained by working in an agency 🏢&lt;/h2&gt;
&lt;p&gt;Working as a developer in an agency allowed me to watch the in&amp;#39;s and out&amp;#39;s of a client-service business, seeing first-hand how the sausage is made - all whilst acquiring valuable knowledge from the others around me... and importantly, all while getting paid a salary.&lt;/p&gt;
&lt;p&gt;I would assume before someone starts a bakery that they have in fact had experience first hand working in a bakery - but this is often not the case with an agency. People can &amp;#39;fall into&amp;#39; starting an agency, often when freelancing turns into outsourcing, that then turns into managing a team, which then means more and more projects and so on. I&amp;#39;m sure this can be an awesome way to get started, but just as the baker will learn a lot from their experience working in another bakery - gaining hands on experience working at an existing agency can be viewed as a risk minimising strategy, and a somewhat simpler path of least resistance before creating your own business.&lt;/p&gt;
&lt;p&gt;I worked at two seperate agencies before starting my own, and being a dev at an agency is one of the biggest ways I learnt the real meaning of &amp;quot;full&amp;quot; in the full-stack. Frontend, backend, database, deployments, server setups, working in a team, having real responsibilities, a little bit of project management, and a little bit of estimation.&lt;/p&gt;
&lt;p&gt;Not all the knowledge you will gain working at an agency will be of the type &amp;quot;hey this is the absolute best way to do it!&amp;quot;, but sometimes more of the type &amp;quot;hmm I don&amp;#39;t think I would do it this way if I was in control&amp;quot; - and that&amp;#39;s great. You can learn what you do and don&amp;#39;t want to do when you start your own business. And this sets a spark in entrepreneurs. We see a problem and know we can do better (whether we actually can or not is not important!), we can&amp;#39;t help but think of the next evolution of things - we zig when others zag.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;If everything was perfect, you would never learn and you would never grow&lt;/em&gt;” ― Beyoncé&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;In my experience smaller agencies can sometimes offer a broader experience than larger agencies, as in a smaller team you will be exposed to all parts of the business as opposed to perhaps being locked in to &amp;quot;frontend developer&amp;quot;.&lt;/p&gt;
&lt;h3 id=&quot;key-learnings-i-gained-being-a-developer-at-an-agency&quot;&gt;Key learnings I gained being a developer at an agency&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Where clients come from, and how the agency handles incoming leads&lt;/li&gt;
&lt;li&gt;How the agency communicates with clients (and potential clients)&lt;/li&gt;
&lt;li&gt;How client projects are managed (including time, cost, and scope overruns)&lt;/li&gt;
&lt;li&gt;The non-technical tools used (e.g. time keeping project management, source control etc)&lt;/li&gt;
&lt;li&gt;How team dynamics and team hierarchy&amp;#39;s work&lt;/li&gt;
&lt;li&gt;How communication works across the team (and between teams if large enough)&lt;/li&gt;
&lt;li&gt;How team roles and responsibilities are assigned (and actioned)&lt;/li&gt;
&lt;li&gt;How a software project gets delivered end-to-end (scoping, development, deployment)&lt;/li&gt;
&lt;li&gt;How the hosting and system infrastructure is managed&lt;/li&gt;
&lt;li&gt;How the business supports projects after delivery&lt;/li&gt;
&lt;li&gt;How the business balances / prioritises existing project support vs&amp;#39;s new projects&lt;/li&gt;
&lt;li&gt;How the business handles down time / not having work&lt;/li&gt;
&lt;li&gt;The culture and how it is cultivated and nurtured&lt;/li&gt;
&lt;li&gt;The pay, and if the company pays below, at, or above the market rate for their staff&lt;/li&gt;
&lt;li&gt;The general happiness of the business and the staff&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;experience-gained-by-freelancing-&quot;&gt;Experience gained by freelancing 🧑🏽‍💻&lt;/h2&gt;
&lt;p&gt;After my time working in an agency, I decided to go out on my own and give freelancing a shot, and I think this was vital to supercharge my business knowledge. Freelancing allows you to get a taste of running the smallest business there is: yourself.&lt;/p&gt;
&lt;p&gt;While getting hands on experience at an agency will show you what the agency life is like, freelancing will ram client-service experience directly down your throat. But in a good way!&lt;/p&gt;
&lt;p&gt;Client communication, sales and marketing, chairing meetings with numerous client stakeholders - If you can gain any of these in advance before starting your agency then that&amp;#39;s a win. I know my freelancing experience took me from a confident developer, to a more well-rounded business dude. And I needed that, as I was getting a little over confident!&lt;/p&gt;
&lt;p&gt;But freelancing humbled me. I went out into the world full of excitement to get great projects, execute them really well, and build a great client base. But my first taste of freelancing was overwhelming. When this didn&amp;#39;t go according to plan who could I blame? When I did win projects could I really execute these all by myself? These were the gems of experience I needed under my belt.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Y&lt;em&gt;ou can’t knock on opportunity’s door and not be ready&lt;/em&gt;” ― Bruno Mars&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Freelancing will show you just how much is involved in running a business - even a tiny business. I definitely took for granted things like the amount of time needed to pitch for projects (and then not win them), the amount of client communication required, all the boring invoice and tax parts, and generally just always looking for work. Besides business running skills, it was my first real experience not going into an office at 9am, so dealing with self-motivation and will-power was a steep learning curve for me.&lt;/p&gt;
&lt;h3 id=&quot;key-learnings-i-gained-from-freelancing&quot;&gt;Key learnings I gained from freelancing&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Being the boss (how you find the responsibility and pressure)&lt;/li&gt;
&lt;li&gt;Handling the unknown and not being in full control&lt;/li&gt;
&lt;li&gt;Sales, marketing, branding, and positioning&lt;/li&gt;
&lt;li&gt;Handling leads, from initial introduction to closing the deal&lt;/li&gt;
&lt;li&gt;Losing leads, and getting back on the horse&lt;/li&gt;
&lt;li&gt;Scoping a project end-to-end&lt;/li&gt;
&lt;li&gt;Estimation (the mystical black art that is)&lt;/li&gt;
&lt;li&gt;Confidently pitching your proposed solution to the client&lt;/li&gt;
&lt;li&gt;Dealing with strict budgets and time sensitive deliveries&lt;/li&gt;
&lt;li&gt;Handling payments and milestones&lt;/li&gt;
&lt;li&gt;Handling changes in scope&lt;/li&gt;
&lt;li&gt;Handling invoices and payments&lt;/li&gt;
&lt;li&gt;The joys of paying tax&lt;/li&gt;
&lt;li&gt;Handling terrible clients&lt;/li&gt;
&lt;li&gt;Firing terrible clients&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;cool-story-bro-but-how-do-i-do-all-that-&quot;&gt;Cool story bro, but how do I do all that? 🤷‍♀️&lt;/h2&gt;
&lt;p&gt;I felt a bit conflicted writing this piece, as whilst I wanted to share some insights on what I took away from two defined stages of my work experience - I also knew this wasn&amp;#39;t particularly actionable advice.&lt;/p&gt;
&lt;p&gt;But in lieu of a mammoth article on how to land a job and how to become a freelancer, I have thrown out on Twitter the advice that I would give if I was just starting out either of these ventures today. Take a look at the tweet (threads) below if you&amp;#39;re interested.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;My thoughts on a how a junior developer can stand out from the crowd when going for jobs...&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;If I was a junior developer applying for a job today, this is what I would do to stand out from the crowd.  &lt;/p&gt;
&lt;p&gt;(Spoiler alert: you don&amp;#39;t need to do much!)  &lt;/p&gt;
&lt;p&gt;Read on... 👇&lt;/p&gt;
&lt;p&gt;- Chris Rickard (@chrisrickard) &lt;a href=&quot;https://twitter.com/chrisrickard/status/1366141662389436417?ref_src=twsrc%5Etfw&amp;amp;ref=devtoagency.com&quot;&gt;February 28, 2021&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;My thoughts on a how an experienced software dev can get into freelancing today...&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;If I was an experienced software developer looking to get into Freelancing today, these are the steps I would take...  &lt;/p&gt;
&lt;p&gt;Read on 👇&lt;/p&gt;
&lt;p&gt;- Chris Rickard (@chrisrickard) &lt;a href=&quot;https://twitter.com/chrisrickard/status/1366506138187956228?ref_src=twsrc%5Etfw&amp;amp;ref=devtoagency.com&quot;&gt;March 1, 2021&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;-&lt;/em&gt;&lt;/p&gt;
</content:encoded></item><item><title>Interview with Matt Stauffer of Tighten</title><link>https://www.devtoagency.com/interview-matt-stauffer-of-tighten/</link><guid isPermaLink="false">61b29142993d27000122b48e</guid><pubDate>Tue, 23 Feb 2021 21:03:58 GMT</pubDate><description>There are just a handful of software agencies which I took inspiration from for my own business, and Tighten [https://tighten.co/] was certainly one of those. A technically focused agency that also cares about humans, Tighten has worked with some well-known clients and are leaders in their chosen technology space - all this while having a relatively small team. When thinking of other voices I'd like to feature on Dev to Agency, Tighten was the first one that popped into my head. Matt Stauffer [</description><content:encoded>&lt;p&gt;There are just a handful of software agencies which I took inspiration from for my own business, and &lt;a href=&quot;https://tighten.co/?ref=devtoagency.com&quot;&gt;Tighten&lt;/a&gt; was certainly one of those. A technically focused agency that also cares about humans, Tighten has worked with some well-known clients and are leaders in their chosen technology space - all this while having a relatively small team. When thinking of other voices I&amp;#39;d like to feature on Dev to Agency, Tighten was the first one that popped into my head.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://mattstauffer.com/?ref=devtoagency.com&quot;&gt;Matt Stauffer&lt;/a&gt; is the co-founder and Technical Director at Tighten, and in this interview I have been lucky enough to pick-his-brain on all things agency related, and hopefully tease out some nuggets of insight that will be helpful for you on your journey.&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2021/12/matt-circle.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;hr&gt;
&lt;h2 id=&quot;can-you-introduce-yourself-to-the-dev-to-agency-readers&quot;&gt;Can you introduce yourself to the Dev to Agency readers?&lt;/h2&gt;
&lt;p&gt;Sure! I’m Matt Stauffer, partner and technical director of Tighten, an agency where we build custom web applications using Laravel, Vue, React, and other web-based technologies. I’m also an author, an online teacher, and I speak on podcasts, YouTube, and at conferences. I live in Atlanta, GA with my two kids and our dog and, when there’s not a global pandemic, like to bike and work with wood in my free time.&lt;/p&gt;
&lt;h2 id=&quot;what-was-your-experience-before-tighten&quot;&gt;What was your experience before Tighten?&lt;/h2&gt;
&lt;p&gt;I started freelance web development in high school (my first paid client was in 2002), taking small projects for friends and community members. At times I worked full time in tech, starting out as an intern at a video production company during summers in high school and later interning as the sole web developer at a .NET shop. But even when I wasn’t working in tech full time, I was still taking on small freelance projects.&lt;/p&gt;
&lt;p&gt;After college I kept up my freelance work but my primary job was a non-technical role at a non-profit, where I worked for five years. After five years, I moved to Chicago and decided to go back into full-time programming, so I tried to pick up enough clients to freelance full time.&lt;/p&gt;
&lt;h2 id=&quot;how-did-tighten-start&quot;&gt;How did Tighten start?&lt;/h2&gt;
&lt;p&gt;In Chicago I worked from a co-working space, and I made it my goal to meet every person there. I’d been working from that space for months and had met everyone except one guy who worked in a closed office all the time. One day I was staying late teaching an old friend about HTML5Boilerplate, and that one person I hadn’t met opened his office door and started heading out. He stopped by my desk and said something like, “Sorry to interrupt, but are you looking for work? I’m trying to hire someone to work in exactly the technologies you’re talking about here for a project.”&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;He was a programmer tired of keeping up with the latest technology who longed to run a business, and I was a programmer tired of trying to get new business who just wanted to dig deep into technology&lt;/em&gt;&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We worked together on that project and then many more, and when I had to move away from Chicago for family reasons, that guy - Dan, now my business partner - proposed we start a company together. So, we did. At first, it was just the two of us; he was a programmer tired of keeping up with the latest technology who longed to run a business, and I was a programmer tired of trying to get new business who just wanted to dig deep into technology.&lt;/p&gt;
&lt;h2 id=&quot;how-do-you-think-yourself-and-co-partner-dan-both-being-software-developers-influences-the-company&quot;&gt;How do you think yourself (and co-partner Dan) both being software developers influences the company?&lt;/h2&gt;
&lt;p&gt;One of our founding ideas behind how we want to run the company has always been “We want to build a company we would want to work for.” Much of what guides this is just humanity - care for people’s personal lives and family. But some of it also comes specifically from our experiences as programmers. For example, many programmers have experienced the miserable expectation to deliver work at a pace that was promised by some non-technical salesperson. That doesn’t happen at Tighten, not just because Dan and I are technical, but more importantly because it’s a key goal for us not to reproduce that dynamic.&lt;/p&gt;
&lt;h2 id=&quot;can-you-remember-how-tighten-found-its-first-clients-and-what-was-your-strategy-to-find-them&quot;&gt;Can you remember how Tighten found its first clients, and what was your strategy to find them?&lt;/h2&gt;
&lt;p&gt;Since Dan and I had both been freelancing for over a decade, our first clients were all our existing clients and networks. We relied heavily on word of mouth from our existing networks and client base as we slowly grew the company.&lt;/p&gt;
&lt;h2 id=&quot;what-challenges-did-tighten-face-in-the-early-years-and-how-did-you-deal-with-them&quot;&gt;What challenges did Tighten face in the early years, and how did you deal with them?&lt;/h2&gt;
&lt;p&gt;We faced a lot of challenges, but I think the hardest had to do with interpersonal issues. Dan and I are both naturally conflict avoidant, and within our first few years we had to fire an employee who was endangering our biggest contract and managed to completely miscommunicate client expectations on a fixed-bid project.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;The end result was me working 60-80 hour weeks for a few months. Not fun, but we survived it&lt;/em&gt;&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This was a miserable experience. Firing someone is not fun, so we endured the problem much longer than we would’ve wanted to, and at first didn’t confront it as directly as we should’ve. It took growth and perseverance to both eventually take the right step, but also to do so feeling like we had given a fair chance for the employee to improve &lt;em&gt;before&lt;/em&gt; firing them. And when we realized how out of sync our expectations were with our client’s expectations, we had to decide whether we could afford to be stubborn or whether we had to cave to the client’s expectations. In this circumstance, we realized that it had been our fault in poor communication, so the end result was me working 60-80 hour weeks for a few months. Not fun, but we survived it.&lt;/p&gt;
&lt;h2 id=&quot;did-tighten-pivot-at-all-over-the-years-e-g-change-focus-&quot;&gt;Did Tighten pivot at all over the years? (e.g. change focus)&lt;/h2&gt;
&lt;p&gt;We’ve always been a consultancy. The only big focus shift we’ve made is from a shop that is scared to embrace a particular tech stack (“we just make web apps, using whatever tech stack makes the most sense”) to one that recognizes that we can both work broadly across tech stacks &lt;em&gt;and&lt;/em&gt; attach ourselves to the technologies we enjoy the most. Now, we’re known as a Laravel shop, although we are also proficient and reputable with React and Vue and a few other technologies.&lt;/p&gt;
&lt;h2 id=&quot;what-do-you-think-sets-tighten-apart-from-other-agencies&quot;&gt;What do you think sets Tighten apart from other agencies?&lt;/h2&gt;
&lt;p&gt;Tighten, first and foremost, cares about people. Dan and I care first about our families and each other, but very immediately after that come our employees and their families. We create policies and practices that honour the individual, that respect the importance of family and mental health, and that encourages honesty, integrity, self-care, and personal and professional growth.&lt;/p&gt;
&lt;p&gt;But we also care deeply about our clients and customers. Our most common way of working is with a team or a founder who doesn&amp;#39;t just need an application or tool built - they also need to learn or to have their teams learn. We work closely with founders or team leads to help them better understand what they need and how best to deliver it, and also work with their teams to help them level up.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;We trust our employees; they trust us; we trust our clients; they trust us&lt;/em&gt;&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;And, as Dan is quick to point out, all of this relies on trust. We trust our employees; they trust us; we trust our clients; they trust us. We don’t have processes that rely on narrow scopes and supervision and legalism; our process and relationships are based on openness, trust, communication, and shared goals.&lt;/p&gt;
&lt;p&gt;And, very importantly, none of this is viable unless we have the absolute best people and help them grow. So, in all this, we work to hire brilliant people with incredible capacity for learning and teaching and growing and problem-solving. Whether or not they know our tech stack, every person who joins our team, from apprentice to lead, possesses those characteristics, so we can confidently say that, when we ask for clients to trust us, it’s not a decision they’ll regret.&lt;/p&gt;
&lt;h2 id=&quot;what-practices-does-tighten-follow-to-ensure-technical-quality&quot;&gt;What practices does Tighten follow to ensure technical quality?&lt;/h2&gt;
&lt;p&gt;We give our programmers 20% time on Fridays to work on internal and open source projects and continue their education. We share our learnings in Slack and Slab, and in monthly lunch and learns. We assign two devs at a time to a project and everyone is assigned only to one project at a time. We encourage pair programming and require all code to have been seen by two programmers, whether via pair programming or code review. We write automated tests for most of our code. And we often write and build new standards and specs for any easily-standardized quality controls.&lt;/p&gt;
&lt;h2 id=&quot;what-are-3-things-you-would-tell-a-developer-who-is-thinking-of-starting-their-own-software-agency&quot;&gt;What are 3 things you would tell a developer who is thinking of starting their own software agency?&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Don’t start a programming business because you love programming; do it because you have some reason to want to start a business&lt;/em&gt;&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;1️⃣ &lt;strong&gt;Don’t do it. But, if you read that and you’re still planning on it, I warned you.&lt;/strong&gt;&lt;br&gt;I always tell people who love doing a thing: the worst way to continue in that direction is to start a business doing that thing. Why? Because you’re now tasked with &lt;em&gt;running a business&lt;/em&gt; and you’ll eventually hire people to do the thing you love. If your greatest joy is in making websites, starting a business is the worst thing you could do, and the easiest way you could limit your time available to code. Don’t start a programming business because you love programming; do it because you have some reason to want to start a business.&lt;/p&gt;
&lt;p&gt;2️⃣ &lt;strong&gt;Don’t do it alone.&lt;/strong&gt;&lt;br&gt;I would’ve lost my mind years ago without Dan, and Tighten wouldn’t be at all what it is today without him. Running a business alone is &lt;em&gt;lonely&lt;/em&gt;. I’ve talked to friends who do it and they don’t recommend it.&lt;/p&gt;
&lt;p&gt;3️⃣ &lt;strong&gt;Pay for an accountant and a lawyer on day one.&lt;/strong&gt;&lt;br&gt;Never try to handle that stuff on your own.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;I hope you enjoyed this interview with Matt. If you did, please hit the &lt;strong&gt;Subscribe Now&lt;/strong&gt; button below for more insights on how to start and run a software development agency.&lt;/p&gt;
&lt;p&gt;If you have any thoughts, feedback, or questions, feel free to reach out to me on Twitter &lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;&lt;/p&gt;
</content:encoded></item><item><title>Do you need a co-founder to start an agency?</title><link>https://www.devtoagency.com/do-you-need-a-cofounder/</link><guid isPermaLink="false">61b29142993d27000122b48d</guid><pubDate>Tue, 16 Feb 2021 07:47:51 GMT</pubDate><description>Do you need a co-founder to run an agency? Do you need a partner in the business, with skin in the game just like you? This is a controversial topic in the startup world, we have Paul Graham saying the number #1 mistake he sees in startups is only having a single founder [http://www.paulgraham.com/startupmistakes.html], and on the other hand there are a bazillion articles telling you why you [https://www.businessinsider.com.au/you-dont-need-a-cofounder-anymore-2010-4?r=US&amp;IR=T] don't [https:</description><content:encoded>&lt;p&gt;Do you need a co-founder to run an agency? Do you need a partner in the business, with skin in the game just like you?&lt;/p&gt;
&lt;p&gt;This is a controversial topic in the startup world, we have Paul Graham saying the number #1  mistake he sees in startups is only &lt;a href=&quot;http://www.paulgraham.com/startupmistakes.html?ref=devtoagency.com&quot;&gt;having a single founder&lt;/a&gt;, and on the other hand there are a bazillion articles telling you why &lt;a href=&quot;https://www.businessinsider.com.au/you-dont-need-a-cofounder-anymore-2010-4?r=US&amp;amp;IR=T&amp;amp;ref=devtoagency.com&quot;&gt;you&lt;/a&gt; &lt;a href=&quot;https://www.indiehackers.com/@basilesamel/you-dont-need-co-founders-aacbdddaf2?ref=devtoagency.com&quot;&gt;don&amp;#39;t&lt;/a&gt; &lt;a href=&quot;https://techcrunch.com/2016/08/26/co-founders-optional/?ref=devtoagency.com&quot;&gt;need&lt;/a&gt; &lt;a href=&quot;https://medium.com/better-new-than-never/you-dont-need-a-co-founder-f97678575135?ref=devtoagency.com&quot;&gt;a co-founder&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;And of course you don&amp;#39;t &lt;em&gt;need&lt;/em&gt; one... but what are the benefits?&lt;/p&gt;
&lt;p&gt;You can try and get things rolling by yourself, and then hire staff as you need. You also technically don&amp;#39;t need experience in the industry, to focus on a niche, or have any existing clients - but these small parts will make your journey easier. And it&amp;#39;s by stacking a lot of &amp;#39;small parts&amp;#39; that gets you to where you want to be.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;I don’t think you need a co-founder. But your business will benefit immensely from having a co-founder&lt;/em&gt;&amp;quot; ― Arvid Kahl, The Bootstrapped Founder&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;benefits-of-having-a-co-founder&quot;&gt;Benefits of having a co-founder&lt;/h2&gt;
&lt;h3 id=&quot;share-the-load-&quot;&gt;Share the load 🐪&lt;/h3&gt;
&lt;p&gt;I know it&amp;#39;s obvious, but I need to say it: starting a software agency is hard, and running a successful software agency is even harder. You will wear a million different hats and work your ass off - all whilst living with a lot of uncertainty (and if you&amp;#39;re anything like me, a lot of self-doubt). Having someone there to share the load will take the pressure off, in this case two heads really can be better than one. You can divide and conquer the facets of the business, whilst playing to your individual strengths. A partner in the business can also help share the emotional load, which is oftentimes greater than the physical load.&lt;/p&gt;
&lt;h3 id=&quot;complimenting-skillsets-&quot;&gt;Complimenting skillsets 🧑🏽‍💻&lt;/h3&gt;
&lt;p&gt;A classic combo is the &amp;#39;the business one&amp;#39; and the &amp;#39;technical one&amp;#39;. In a small software business I believe it&amp;#39;s valuable that both partners have at least some technical skills, but importantly at least one of you needs  the business skills - or is prepared to learn fast. Although I think both being technical proficient is important, as with all humans you will have your individual strengths and weaknesses - and this is a bonus.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Co-founders shouldn&amp;#39;t excel in the same areas - it&amp;#39;s inefficient and will inevitably lead to conflicts down the road&lt;/em&gt;&amp;quot; ― Julia Hartz, CEO of Eventbrite&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A perfect unity is one likes sales (and coding), and one loves to push out code. But perhaps one of you is stronger on the backend and one on the frontend. One super experienced in complex SQL, and the other has an eye for design. Whatever it is - complimentary skills between business partners is a super power, and you don&amp;#39;t want a partner that is just a mirror image of you.&lt;/p&gt;
&lt;h3 id=&quot;partners-in-strategy-&quot;&gt;Partners in strategy ♟&lt;/h3&gt;
&lt;p&gt;A lot of business is strategy, future planning, and making important decisions. Whilst your life-partner or a mentor may be a fantastic sounding board, a canny business partner who is actually in the trenches with you already is the best strategist, as they understand the domain and issues at hand. Decisions such as hiring staff, taking on a very large project, or even pivoting to an industry or technology niche - can all be difficult to make on by yourself. And will put a lot of weight resting solely on your shoulders.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Don’t do it alone. I would’ve lost my mind years ago without Dan, and Tighten wouldn’t be at all what it is today without him. Running a business alone is lonely. I’ve talked to friends who do it and they don’t recommend it.&lt;/em&gt;&amp;quot; ― Matt Stauffer, Partner and Technical Director of Tighten&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I&amp;#39;ve personally found I need to talk most things through with my business partners, and I know that&amp;#39;s something I will always need to do. Whether it&amp;#39;s a conversation that ends in agreement, or a challenging conversation that brings up differences of opinion - it&amp;#39;s all valuable. Although it&amp;#39;s hard for me to accept - I don&amp;#39;t know everything, and sometimes I need to have my opinion changed.&lt;/p&gt;
&lt;h2 id=&quot;negatives-&quot;&gt;Negatives? 😔&lt;/h2&gt;
&lt;p&gt;A toxic founder relationship can bring a business to its knees. Bad partners are a risk, and embarking on a business with someone is not a decision that should be taken lightly.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“&lt;em&gt;A lot of people treat choosing their cofounder with even less importance than they put on hiring. Don’t do this.&lt;/em&gt;” ― Sam Altman, CEO of OpenAI&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It&amp;#39;s a cliché, but in many respects a business relationship is like a romantic relationship:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You need to take it seriously&lt;/li&gt;
&lt;li&gt;You both need to be in it for the right reasons&lt;/li&gt;
&lt;li&gt;You need to have respect for your partner&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If any of these are misaligned then it may be a rocky path ahead.&lt;/p&gt;
&lt;p&gt;So how do you ensure a good match with your co-founder? Arvid Kahl &lt;a href=&quot;https://thebootstrappedfounder.com/co-founder/?ref=devtoagency.com&quot;&gt;has a good list of key alignments to look for in a co-founder relationship&lt;/a&gt;, and in my experience his advice is worth its weight in gold. Without communication it can&amp;#39;t last, without personality alignment resentment will sneak in, and without empowering each other to drive and push through the hard times, you may just both give up.&lt;/p&gt;
&lt;p&gt;I have a had a few businesses so far, and my experience with co-founders has not always been 100% perfect, but I don&amp;#39;t look back and wish I had of done any of them alone.&lt;/p&gt;
&lt;p&gt;One thing I will say is more co-founders is not better.&lt;/p&gt;
&lt;p&gt;Two complimentary humans is a great team, two people can support and improve each other to be more than the sum of its parts. Of course three, four, and five people can also improve each other. But adding more partners to a business is not simple math, it doesn&amp;#39;t always accumulate impact in the way you expect. More people means more personalities, more opinions, and more decisions requiring a larger consensus. Just as I&amp;#39;m sure many software agencies have nailed it with just a single founder, there is bound to be as many who found success with three, four, or five founders.&lt;/p&gt;
&lt;p&gt;I have started businesses with two founders, three founders - and four founders. And after all this experience, I am pretty sure my future businesses will only have two founders. Two people to share the load, steer the ship, support each other and make decisions - and then hire in great people when there is too much work to do yourself.&lt;/p&gt;
&lt;h2 id=&quot;how-do-i-find-a-co-founder-&quot;&gt;How do I find a co-founder? 🔎&lt;/h2&gt;
&lt;p&gt;Hopefully you already know your soon to be co-founder, that is the path of least resistance. An existing friend or colleague you respect and could imagine starting a business with.  But let&amp;#39;s assume you don&amp;#39;t already have an acquaintance that matches the criteria you are looking for, then my friend, you are going to have to hunt.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;If you&amp;#39;re an engineer, go to developer meetups or work on open source projects, or go to hackathons. Do things where others, engineers and builders are hanging out&lt;/em&gt;&amp;quot; ― Harj Taggar, Co-founder and CEO of Triplebyte&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;There is no magic answer to this, you need to align yourself with places your mysterious co-founder could be hanging out. Events and communities, online or offline, it doesn&amp;#39;t matter. Meet more people, engage in more conversations, and increase your luck surface area.&lt;/p&gt;
&lt;p&gt;I have already made comparisons to founders and romantic relationships - and being on the lookout for a co-founder is no different. It is the same as dating, in that even by acknowledging the fact you are looking for a partner, potential partners will start to be appear in your world. This isn&amp;#39;t magic conjuring int up, it is your brain pattern matching and keeping your desires in your consciousness. But by no means is just &amp;#39;being on the lookout&amp;#39; the answer, you need to put yourself out there, and get in the situations that will reside in you finding more candidates.&lt;/p&gt;
&lt;p&gt;And the dating analogy doesn&amp;#39;t end when you have found a potential co-founder. In fact that&amp;#39;s where the real dating part begins. Co-founder dating is a thing, take a read of the &lt;a href=&quot;https://firstround.com/review/the-founder-dating-playbook-heres-the-process-i-used-to-find-my-co-founder/?ref=devtoagency.com&quot;&gt;The Founder Dating Playbook&lt;/a&gt; if you want some interesting advice on how to manage the fledgling relationship, and decide on whether this person is truly &amp;#39;co-founder material&amp;#39;.&lt;/p&gt;
&lt;h2 id=&quot;can-i-just-do-it-by-myself-&quot;&gt;Can I just do it by myself? 🕺&lt;/h2&gt;
&lt;p&gt;Yes. But an agency of just you is not an agency - it is you as a freelancer.&lt;/p&gt;
&lt;p&gt;An agency needs many hands. Hands to serve the current clients, whilst other hands are looking for the next clients. Technically all these hands could be yours, it&amp;#39;s not impossible, but it will be a hard road ahead. If this is what you want I would recommend you have a solid plan in place on how to balance sales with building, how to build a pipeline of work, and at what point will you hire staff. I would also recommend a strong support network, people you can turn to instead of a business partner to help provide advice, mentorship, and also help with strategy.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;A wise man has to always listen to the peers he surrounds around himself. That&amp;#39;s why you surround yourself with other smart people. Captain Kirk keep Mr. Spock right beside him&lt;/em&gt;&amp;quot; ―RZA, Wu-Tang Clan&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;For me, starting an agency meant having a bigger impact. I wanted to serve many clients, build a team, and work on large interesting projects. I also wanted to eventually scale back from doing &amp;#39;everything&amp;#39; to mainly focusing on the parts I enjoyed the most.&lt;/p&gt;
&lt;p&gt;Sure, it always required hard work - but for me having co-founders made it manageable. In the end I was able to stop working so hard and enjoy the benefits of the well-oiled machine that I had helped build from the ground up.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If you have any thoughts, feedback, or questions, I would love to hear from you. Please hit me up on Twitter &lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;&lt;/p&gt;
</content:encoded></item><item><title>Million dollar consulting</title><link>https://www.devtoagency.com/million-dollar-consulting/</link><guid isPermaLink="false">61b29142993d27000122b48c</guid><pubDate>Thu, 04 Feb 2021 08:16:42 GMT</pubDate><description>Apologies in advance, this article is not a step-by-step guide on how to build a consulting company to a cool 1 million - it is in fact a book recommendation. The book is aptly titled Million Dollar Consulting: The Professional's Guide to Growing a Practice [https://alanweiss.com/shop/books/paperback/million-dollar-consulting/] and is written by Alan Weiss. This is not an affiliate post, I'm writing about this book because I dig it, and I hope some of you dig it too. &gt; &quot;Million Dollar Consulti</description><content:encoded>&lt;p&gt;Apologies in advance, this article is not a step-by-step guide on how to build a consulting company to a cool 1 million - it is in fact a book recommendation.&lt;br&gt;The book is aptly titled &lt;a href=&quot;https://alanweiss.com/shop/books/paperback/million-dollar-consulting/?ref=devtoagency.com&quot;&gt;Million Dollar Consulting: The Professional&amp;#39;s Guide to Growing a Practice&lt;/a&gt; and is written by Alan Weiss. This is not an affiliate post, I&amp;#39;m writing about this book because I dig it, and I hope some of you dig it too.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Million Dollar Consulting teaches you how to build a thriving consultancy business, by focusing on relationships, delivering strategic value and thinking long-term all the way through.&lt;/em&gt;&amp;quot; ― Four Minute Books&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;One of the reasons I decided to start Dev to Agency was because when I was starting out in 2012 I struggled to find good actionable information. Startups were the hot thing (and still are!), but finding content I felt would help me in my quest for starting a custom software agency was hard work. I was recommended this book many years ago on Hacker News, and although it&amp;#39;s 25 years old, the vast majority of it still rings true today (a large part of the book was rewritten/modernised in 2016).&lt;/p&gt;
&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2021/12/milliondollarconsulting-640x640.jpg&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;p&gt;I have mentioned before that I don&amp;#39;t like the term &amp;#39;agency&amp;#39;, and I never really referred to my business as an agency. Instead I would say a &amp;#39;Custom software business&amp;#39; or a &amp;#39;Custom software consultancy&amp;#39; - but as the majority of the world (and potential clients) use the term agency, I have chosen to use that term.&lt;/p&gt;
&lt;p&gt;I say this because when searching for information online I actually often use the term &amp;#39;consultancy&amp;#39; or &amp;#39;consultant&amp;#39;. Agencies, consultancies, freelancers - we all provide client services so the lines get blurry. However consultancies are generally perceived as having higher expertise (whether that&amp;#39;s true or not) - so advice on how to build a million dollar consulting business is certainly relevant to building a quality software agency.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“W&lt;em&gt;hen people knock on your door, credibility is assumed and fees are whatever you say they are&lt;/em&gt;.” ― Alan Weiss, Million Dollar Consulting&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Ok enough of that, let&amp;#39;s get to the reason I am recommending you read this book. Alan Weiss is a leader in the consulting field (I also recommend reading Alans other books such as The Consulting Bible) - and one of the things he is best at is convincing builders (us), that this is not all about building - but all about the clients. The value you give them, the relationships you build with them, and the trust that you forge together. It can all sound a bit fluffy - but this book gave me a reality check when starting out, because as a technologist it&amp;#39;s easy to get carried away about the technology.&lt;/p&gt;
&lt;p&gt;Even though a bunch of the book was updated in 2016, don&amp;#39;t expect there to be a chapter on &amp;#39;Building instagram followers&amp;#39;. You can read a billion books on that topic, but strategically building high-value client relationships and sharpening your expertise - this is not a dime-a-dozen type book. This is advice from a weary battle-worn expert who has spent years in the trenches honing his craft. Look past the ageing examples, and think about how these tested learnings can apply to you.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;You grow based on exploiting strengths, not by acclimating to weaknesses.&lt;/em&gt;&amp;quot; ― Alan Weiss, Million Dollar Consulting&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;key-takeaways-from-million-dollar-consulting-&quot;&gt;Key takeaways from Million Dollar Consulting 🔑&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;A consultant adds value to their customers cause.&lt;/li&gt;
&lt;li&gt;Get discovered by making yourself visible.&lt;/li&gt;
&lt;li&gt;Focus on the big picture and don’t let your job get in the way of your career.&lt;/li&gt;
&lt;li&gt;Be crystal clear about your strategic goals.&lt;/li&gt;
&lt;li&gt;Sometimes you need to fire clients in order to grow.&lt;/li&gt;
&lt;li&gt;Consulting is a &amp;#39;relationship business&amp;#39; so a likeable brand is crucial.&lt;/li&gt;
&lt;li&gt;Focus on value and partnership when negotiating with a potential client.&lt;/li&gt;
&lt;li&gt;Don’t charge for time, but instead for value.&lt;/li&gt;
&lt;li&gt;Don’t be fooled by immediate success, and always keep your pipeline evenly filled.&lt;/li&gt;
&lt;li&gt;Diversification and investment are the best protections against bad times.&lt;/li&gt;
&lt;li&gt;Think long term and wise up if you want to hold on to your dream client.&lt;/li&gt;
&lt;li&gt;Balance work and life - your real wealth is your free time.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;p&gt;If you&amp;#39;re interested in checking it out &lt;a href=&quot;https://www.amazon.com/gp/product/1259588610?ref=devtoagency.com&quot;&gt;Amazon&lt;/a&gt; has the book in all the formats, and Alan also has it directly for sale &lt;a href=&quot;https://alanweiss.com/shop/books/paperback/million-dollar-consulting/?ref=devtoagency.com&quot;&gt;on his website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Any book recommendations that have helped you? Lets share the knowledge, simply &lt;a href=&quot;https://twitter.com/chrisrickard/status/1357223492937109507?ref=devtoagency.com&quot;&gt;reply to my tweet&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Freelancers and Agencies - what book recommendations have helped your business?  &lt;/p&gt;
&lt;p&gt;My vote is &amp;quot;Million Dollar Consulting&amp;quot; by Alan Weiss &lt;a href=&quot;https://twitter.com/BentleyGTCSpeed?ref_src=twsrc%5Etfw&amp;amp;ref=devtoagency.com&quot;&gt;@BentleyGTCSpeed&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;- Chris Rickard (@chrisrickard) &lt;a href=&quot;https://twitter.com/chrisrickard/status/1357223492937109507?ref_src=twsrc%5Etfw&amp;amp;ref=devtoagency.com&quot;&gt;February 4, 2021&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
</content:encoded></item><item><title>Small can be great</title><link>https://www.devtoagency.com/small-can-be-great/</link><guid isPermaLink="false">61b29142993d27000122b48b</guid><pubDate>Thu, 28 Jan 2021 06:42:17 GMT</pubDate><description>Instead of pretending to be big, your small software agency should be honest and proud of its size. You have strengths that larger agencies don't have, and in my experience if you play to those strengths, then small can achieve great things. &gt; &quot;A small law firm, accounting firm, or ad agency is succeeding because they’re good, not because they’re big.&quot; ― Seth Godin That personal touch 🤝 No one knows a business better than the owner. You know your niche, experience, and the unique path you cros</description><content:encoded>&lt;p&gt;Instead of pretending to be big, your small software agency should be honest and proud of its size. You have strengths that larger agencies don&amp;#39;t have, and in my experience if you play to those strengths, then small can achieve great things.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;A small law firm, accounting firm, or ad agency is succeeding because they’re good, not because they’re big.&lt;/em&gt;&amp;quot; ― Seth Godin&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;that-personal-touch-&quot;&gt;That personal touch 🤝&lt;/h2&gt;
&lt;p&gt;No one knows a business better than the owner. You know your niche, experience, and the unique path you crossed to get to this point. This gives you an irreplaceable insight when it comes selling the gifts of your businesses - and I know firsthand that projects my agency won were directly from me being there in the room. One business owner talking directly to another business owner about the problem they have, and me letting them know that our experience and niche focus will be able to solve it for them.&lt;/p&gt;
&lt;p&gt;In my agency I would personally put the proposal together, I would deliver the pitch to the client, I would architect and oversee the technical delivery, I was there every step of the way. Whilst I didn&amp;#39;t have to write every line of code or be the one to respond to every single email - clients still knew that I was always there to guide and steer towards success, and it wasn&amp;#39;t only my agency they could count on, but also me personally. My clients often remarked how much they valued this personal touch from me - and this in turn created long lasting relationships.&lt;/p&gt;
&lt;h2 id=&quot;increased-efficiency-&quot;&gt;Increased efficiency 🏎&lt;/h2&gt;
&lt;p&gt;An unsuccessful project delivery is rarely caused by a technology problem, it&amp;#39;s usually a communication problem - and small teams can communicate far simpler than a larger teams.&lt;/p&gt;
&lt;p&gt;Jeff Bezos famously said that &amp;quot;If a team cannot be fed by two pizzas, then that team is too large&amp;quot;. This two-pizza-rule specifically speaks to the inefficiencies of communication in a larger group - as teams get bigger the more points of communication that are needed - and this increases exponentially. A small team can get every team member on the same page via a quick 15 minute  stand-up, but this cannot scale to 50 team members. At that size more processes need to be introduced to make sure the right people are in the right meetings, and that they then relay the right information to the right subordinates, and so on.&lt;/p&gt;
&lt;p&gt;Whilst your small software agency cannot deliver ten projects in parallel, it can deliver one to two high-quality projects with far less overhead than a business ten times larger - and with less meetings, rituals, and layers of management - it can be delivered in a smaller amount of time.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;With a small team, you need people who are going to do work, not delegate work. Everyone’s got to be producing.&lt;/em&gt;&amp;quot; ― Jason Fried, ReWork&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A &lt;a href=&quot;https://www.qsm.com/risk_02.html?ref=devtoagency.com&quot;&gt;study&lt;/a&gt; in 2005 by QSM shows that smaller teams of less than 5 people can achieve extraordinarily results as compared with larger teams of 20 or more people. The study compared a database for 4000 similar projects (of around 100k lines of source code), and found on average the smaller team delivered the project just one calendar week longer than the (significantly) larger team. Not only that, but using a smaller team to deliver the same result, the client saved on average $1.84 million dollars compared to the larger (amazingly inefficient) teams.&lt;/p&gt;
&lt;h2 id=&quot;being-nimble-&quot;&gt;Being nimble 🐰&lt;/h2&gt;
&lt;p&gt;Change is inevitable - and oftentimes completely out of your hands. What is in your hands however is the ability to efficiently and effectively respond to change. The slower moving elephant may struggle to fend off a surprise attack from a cheetah, but the more agile rabbit may have better chance at quickly veering of course, and adapting to the unexpected change.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;There is the opportunity to do more and better if you&amp;#39;re smaller and more nimble.&lt;/em&gt;&amp;quot; ― Marc Andreessen, Entrepreneur and investor&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Just because you&amp;#39;re a small doesn&amp;#39;t necessarily mean you are nimble, in fact you could have a very rigid small business that cannot adapt to change at all. The advantage small businesses have is that it&amp;#39;s easier to &lt;em&gt;learn&lt;/em&gt; to be nimble, to &lt;em&gt;practise&lt;/em&gt; moving fast when new opportunities arise. When an unexpected event can be quickly handled by a small group of people around a coffee table (or even better, over a shared pizza) - this is nimble. When it takes a series of bi-weekly meetings, this is not nimble.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;There are of course some challenges about being small, but it&amp;#39;s important to embrace and celebrate that small can be great. Not just &amp;quot;great for a small company&amp;quot; - but great.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If you have any thoughts, feedback, or questions, I would love to hear from you. Please hit me up on Twitter &lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;&lt;/p&gt;
</content:encoded></item><item><title>Think niche</title><link>https://www.devtoagency.com/think-niche/</link><guid isPermaLink="false">61b29142993d27000122b48a</guid><pubDate>Thu, 21 Jan 2021 06:51:42 GMT</pubDate><description>We build web and mobile applications - that's the generic website tagline 90% of your competitors will have. They all look the same, all talk the same, and are all pitching for the same clients as you are. &gt; &quot;If everybody is doing it one way, there's a good chance you can find your niche by going exactly in the opposite direction&quot; ― Sam Walton, entrepreneur and founder of Walmart A niche is a &quot;specialised segment of the market for a particular kind of product or service&quot;, and when applied to so</description><content:encoded>&lt;p&gt;We build web and mobile applications - that&amp;#39;s the generic website tagline 90% of your competitors will have. They all look the same, all talk the same, and are all pitching for the same clients as you are.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;If everybody is doing it one way, there&amp;#39;s a good chance you can find your niche by going exactly in the opposite direction&amp;quot;&lt;/em&gt; ― Sam Walton, entrepreneur and founder of Walmart&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A niche is a &amp;quot;&lt;em&gt;specialised segment of the market for a particular kind of product or service&lt;/em&gt;&amp;quot;, and when applied to software agencies, it means you don&amp;#39;t just specialise in &amp;quot;web and mobile applications&amp;quot; like the rest, but instead you carve out a specific focus area. A focus area that your agency becomes an authority in, allowing you to provide deep value to your clients, and in turn charge a premium for your specialised expertise.&lt;/p&gt;
&lt;p&gt;For your small software agency to punch above its weight and deliver high quality work, I believe focusing on a niche is a superpower to get you there faster.&lt;/p&gt;
&lt;h2 id=&quot;why-should-software-agencies-focus-on-a-niche&quot;&gt;Why should software agencies focus on a niche?&lt;/h2&gt;
&lt;h3 id=&quot;1-increased-authority-&quot;&gt;1. Increased authority 📢&lt;/h3&gt;
&lt;p&gt;Authority is key to attracting clients and showing your competency in your field, but unfortunately gaining authority is especially challenging when just starting out. How can you build authority in a specific area when your first few projects are all so vastly different? An API integration for an old eLearning platform, a mobile app to track walking your dog, and a community website for financial advisors to exchange ideas - what area are you an authority in? Of course you can highlight your &amp;quot;high quality&amp;quot; or your &amp;quot;cheaper rates&amp;quot; - and this is what the other 90% do. But what if instead of your website tagline being &amp;quot;We build web and mobile applications&amp;quot; it said &amp;quot;Experts in delivering internal business software&amp;quot; or instead of &amp;quot;Technology specialists&amp;quot; it said &amp;quot;Specialists in building mobile apps for your startup&amp;quot;. A clearer value proposition for potential clients that succinctly captures what you do best, and what niche you play in.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s obviously more than just your website tagline, but if your entire website is focused on the single specific problem you solve, it makes the sale a lot easier. Say potential client lands on your site, they can see right off the bat that you not only specialise in mobile apps, but more specifically, you focus on startups just like them. This draws them in, and as they scroll down they see some images of startup apps you have delivered along with positive testimonials from founders just like them. They call your phone number, and your conversation with them continues to reinforce your experience and authority with working for people &lt;em&gt;just like them&lt;/em&gt;. You now stand out from the rest, your agency has increased authority in the eyes of the buyer, and that gives you a competitive edge.&lt;/p&gt;
&lt;h3 id=&quot;2-reduced-competition-&quot;&gt;2. Reduced c&lt;strong&gt;ompetition 🏆&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;If you&amp;#39;re the only software agency in your city, then you are one lucky bastard. But unfortunately I don&amp;#39;t think you will be. Your small agency will most likely be one of many around your geographical area, along with the hundreds of freelance software developers that are looking for work. Besides the physical world there are also the millions of competitors on the internet, and as business being conducted fully online is becoming more and more normal, remote competitors is a bigger consideration.&lt;/p&gt;
&lt;p&gt;You already know all this, and it&amp;#39;s a big reason why starting is scary - but you don&amp;#39;t have to run the same race as all those competitors. You can instead run your own race, and separate yourself from the pack by targeting a specific subset of clients, and by solving a specific subset of problems. If you were to specialise in &amp;quot;web and mobile apps&amp;quot; then you have twice the competition as those that specialise in just &amp;quot;mobile apps&amp;quot;. If you niched down even further and focused on &amp;quot;mobile apps for startups&amp;quot; your competition is reduced even further, or &amp;quot;mobile apps for financial startups&amp;quot; even further still. In such a competitive space as software development, reducing competition is huge.&lt;/p&gt;
&lt;h3 id=&quot;3-laser-focus-&quot;&gt;3. Laser focus 🔍&lt;/h3&gt;
&lt;p&gt;Don&amp;#39;t be misled by the &amp;quot;small&amp;quot; in small business, there will be a very gigantic number of priorities competing for your attention. On top of the normal business owner things, you may be getting familiar with how &amp;quot;Karate competition scoring&amp;quot; works for a project you are about to start, grappling with submitting a React native mobile app to all the different app stores, all whilst researching how blockchain works for an upcoming project your pitching for. Focusing on one niche can help you regain some control and realise projects that are not aligned with your niche are really just distractions. You realise the blockchain project is actually not an area you want to work in - and that&amp;#39;s good, you can&amp;#39;t be an expert in everything, and your clients deserve an expert.&lt;/p&gt;
&lt;p&gt;Minimising distractions allows a laser focus on what is really important. Focus on having a concise and memorable sales experience demonstrating your niche authority, focus on gaining even deeper experience in your niche, focus on delivering amazing projects in your niche (and possibly writing great content on your niche), focus on training your staff in your niche - all of this could be more valuable than researching blockchain for a project that doesn&amp;#39;t align with the work you want to focus on.&lt;/p&gt;
&lt;h3 id=&quot;4-depth-of-experience-&quot;&gt;4. Depth of experience 👨‍🏫&lt;/h3&gt;
&lt;p&gt;You may not be an expert from the first day you start your agency, but to separate yourself from the generic masses you should aim to become one as fast you can. Being able to provide you clients with deep, expert experience in their problem area is one of the biggest differentiators out there. And it will open up far more doors than any well-crafted website tagline ever can. Experience compounds, and if you concentrate on a niche, you will win more projects in that niche, allowing you to become an expert quicker than if you take every project that pops its head up. As your experience in your niche deepens you become even more valuable to your clients - and this is what can take you from being viewed as just a &amp;quot;dev shop&amp;quot; to being viewed as a high value partner.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;No one achieves greatness by becoming a generalist. You don&amp;#39;t hone a skill by diluting your attention to its development. The only way to get to the next level is focus&lt;/em&gt;&amp;quot; ― John C. Maxwell&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;At the end of the day a dev shop and a high value partner are both just delivering client services, however it&amp;#39;s deep expertise and knowledge which is the true value to the client, and is what will allow you cross that chasm into becoming an indispensable technology partner.&lt;/p&gt;
&lt;h3 id=&quot;5-expert-rates-&quot;&gt;5. Expert rates 💵&lt;/h3&gt;
&lt;p&gt;Unfortunately it&amp;#39;s common for agencies to use the &amp;quot;race to the bottom&amp;quot; pricing strategy, which is basically who can do it the cheapest (especially common with outsourced dev shops). There may be a time where you price as low as you can just to win a project (especially when starting out), but then move as fast as you can to charging what you are really worth. Separate yourself from the cheaper crowd, and instead aim for the exclusive expert crowd. Obviously this is the dream right? No one wants to be viewed as cheap, but how do you compete with those that charge $7 per hour? Charging what you&amp;#39;re worth is tied to being seen as an expert. Experts charge a premium because they know more than the others (or appear to know more). Experts have the deep experience gained from fighting many battles in the trenches, and it&amp;#39;s that experience the clients pay for. Having a niche will allow you focus on gaining deeper experience, which will in turn help you charge more, which in turn will make life a lot easier.&lt;/p&gt;
&lt;h2 id=&quot;possible-negatives-of-niche&quot;&gt;Possible negatives of niche?&lt;/h2&gt;
&lt;h3 id=&quot;being-pigeonholed-&quot;&gt;Being pigeonholed 🐦&lt;/h3&gt;
&lt;p&gt;Being known as the company that &amp;quot;just does X&amp;quot; could leave you feeling trapped, especially if &amp;quot;X&amp;quot; is not truly something you want to do - or there are not enough clients that actually want &amp;quot;X&amp;quot;. To mitigate this it is important to discover a niche area that is at the intersection of&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Something you are interested in and want to do&lt;/li&gt;
&lt;li&gt;Something you are experienced in (or can gain experience in)&lt;/li&gt;
&lt;li&gt;Something that the market wants (that people will pay for)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Without any of these your niche may feel more like a pigeonhole.&lt;/p&gt;
&lt;h3 id=&quot;reduced-market-&quot;&gt;Reduced m&lt;strong&gt;arket 📈&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;If a pie represents &amp;quot;all possible clients that want custom software&amp;quot;, then yes, your niche is a reduced portion of that pie. That&amp;#39;s a fact. The total possible market for custom software is no longer your target market, and this a bi-product of niching down. However with the right niche this is not a negative thing, as a small company cannot waste time talking with thousands of potential clients that ultimately choose another agency. A small software agency doesn&amp;#39;t need or want thousands of customers like a $5 per month SaaS app does. You want a small group of quality clients who respect you and value your work (that&amp;#39;s the goal). There is plenty of work out there for everyone, and as long as you don&amp;#39;t pick too small a niche, then a smaller market is not a bad thing.&lt;/p&gt;
&lt;h3 id=&quot;the-expert-barrier-&quot;&gt;The e&lt;strong&gt;xpert barrier 🚧&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;How does your agency become an expert in anything if you are just starting out? This is the chicken or the egg problem, you cannot become the industry leading expert if you don&amp;#39;t get the experience. This is a common barrier of entry when deciding on whether to focus or remain a generalist - but every expert had to start somewhere.&lt;/p&gt;
&lt;p&gt;My advice is: As honestly as you can, &amp;quot;fake it till you make it&amp;quot;. I am not telling you to lie about being specialist in something you have no experience in (but I also don&amp;#39;t think you should choose a niche you have zero experience in), I am saying to creatively highlight the experience you DO have - no matter how limited - and focus communicating the benefits of what you can do with that experience. This is sales, and oftentimes you need to sell where you want to be as opposed to where you are right now tomorrow. I would also recommend immersing yourself in your niche. Read all you can, talk to as many people as you can, and ask all the questions you can. You need to be pro-active to become an expert, and the knowledge that you gain today will compound as your expertise grows.&lt;/p&gt;
&lt;h3 id=&quot;niche-regret-&quot;&gt;Niche regret 😔&lt;/h3&gt;
&lt;p&gt;Ok but what do you do if you have tried everything and the niche you focused on is just not working? You&amp;#39;ve spent all this time crafting your agency as the &amp;quot;Experts in Blah Blah Blah&amp;quot;, do you just write it off as a sunk cost? Not to mention - what will your clients think? First of all, your learnings are not a sunk cost. These types of experiences are indispensable and cannot truly be learnt without having gone through it. Don&amp;#39;t stress about changing your niche, in the startup world this is called a pivot, and has famously been responsible for some of the biggest companies (did you know the multi-billion dollar communications company Slack started as an interactive game?).&lt;/p&gt;
&lt;p&gt;The only thing I would advise is not switch your niche at the drop of a hat. Think about it. But when you are certain that a niche is not for you, then don&amp;#39;t have regrets and move on. It&amp;#39;s not a failure, there are plenty more niches in the sea. If you already have a number of established clients in your niche, you don&amp;#39;t need to fire them if you change your niche (unless of course you want to) - and you don&amp;#39;t need to completely abandon your first niche. Having more than one niche whilst being careful not to fully divide your focus, can work out great. Just make sure your value offering is still clear and not confusing to potential clients. This was similar to my experience, we changed niches after a while, and whilst we would still work with the previous clients in the original niche - our website, communications, and focus was on our new niche.&lt;/p&gt;
&lt;h2 id=&quot;my-experience-with-agency-niches-&quot;&gt;My experience with agency niches 📔&lt;/h2&gt;
&lt;p&gt;Before starting my agency, my co-founder and I had previously been involved in startups. The year prior my startup had been through an accelerator program, and I had just recently returned from San Francisco before I started freelancing. When we decided to start an agency it was an easy decision for us to focus on startups as a niche. More specifically, we chose to focus on working with early-stage startups to develop their first MVP (minimum viable product) around a price point we felt was competitive enough to get us off the ground as a business - but profitable enough to not feel like we were selling our souls.&lt;/p&gt;
&lt;p&gt;We already had connections in the startup ecosystem so we reached out to as many people as we could. We had targeted our websites communication to reflect our focus, and offered some productised services such as a &amp;quot;full day MVP roadmap workshop&amp;#39; for a once-off price. This worked well, we got our first handful of clients and our first real taste of agency experience. After a while we began to find many clients didn&amp;#39;t provided ongoing work, and some we never hear from after the project delivery. This was because many of them fizzled out as they failed to find product/market fit fast enough, or failed to raise money We realised whilst the MVP&amp;#39;s for startups niche worked great to get things up and running, we believed a different niche would need to be incorporated in order to really move things forward.&lt;/p&gt;
&lt;p&gt;Around the same time someone I had worked with many years prior reached out. They knew we focused on startups, but wondered if we would want to help out their medium sized boring business on a large software project to automate their internal workflow practises. This interested us, so we put together a proposal, and won the project. Not only was it a success, but found we really enjoyed getting to know how their specific business and its industry functioned. Helping this business improve their existing internal process gave us more enjoyment than building the next startup idea (Facebook for Dogs?) - and it turned out to be a perfect juncture for us to explore another niche, internal software for business automation. This niche had the added benefit of serving businesses who had been around for a while and made money - unlike those fresh-faced startups (no offence startups!). We soon decided to move our focus from &amp;quot;MVP&amp;#39;s for startups&amp;quot; to  &amp;quot;internal business software (for boring businesses)&amp;quot;.  This niche was still pretty broad, and looking back I think we could have focused event deeper (a few years later we ultimately ended up focusing only on a few key industries). Whilst we still would do startup work if the right project came along, we updated our websites communication to reflect this new niche. We started to actively target medium sized un-sexy businesses, and specifically started to blog about concepts such as &amp;quot;Business process automation&amp;quot; and &amp;quot;Legacy system rebuilds&amp;quot;. We eventually started to win more work in the niche, and in turn gained deeper expertise. Word-of-mouth introductions from important clients started to play a larger role as our authority grew. This niche proved much more successful than our original - but we needed the experience of our first niche to really get experience running an agency.&lt;/p&gt;
&lt;p&gt;Whilst we found our first niche due to industry experience, our second niche found us - and we were lucky it found us at the right time when we were open to receive it.&lt;/p&gt;
&lt;h2 id=&quot;some-possible-software-agency-niches-&quot;&gt;Some possible software agency niches 🗂&lt;/h2&gt;
&lt;p&gt;For your software agency there are two real categories of niches:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Industry niches - e.g. the legal industry, where you focus on clients in the same industry.&lt;/li&gt;
&lt;li&gt;Project type niches - e.g. &amp;quot;legacy software rebuilds&amp;quot;, where you focus on clients that have the same type of project they need delivered.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Some examples of industry niches are:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automotive&lt;/li&gt;
&lt;li&gt;Banking&lt;/li&gt;
&lt;li&gt;Education&lt;/li&gt;
&lt;li&gt;Engineering&lt;/li&gt;
&lt;li&gt;Energy&lt;/li&gt;
&lt;li&gt;Financial&lt;/li&gt;
&lt;li&gt;Government&lt;/li&gt;
&lt;li&gt;Healthcare&lt;/li&gt;
&lt;li&gt;Jewellery&lt;/li&gt;
&lt;li&gt;Legal&lt;/li&gt;
&lt;li&gt;Manufacturing&lt;/li&gt;
&lt;li&gt;Real estate&lt;/li&gt;
&lt;li&gt;Telecommunications&lt;/li&gt;
&lt;li&gt;Transportation&lt;/li&gt;
&lt;li&gt;Not-for-profit&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Some example project type niches are:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;APIs / Integrations&lt;/li&gt;
&lt;li&gt;Blockchain&lt;/li&gt;
&lt;li&gt;Data transformation&lt;/li&gt;
&lt;li&gt;Desktop software (too broad by itself)&lt;/li&gt;
&lt;li&gt;Ecommerce software&lt;/li&gt;
&lt;li&gt;Games&lt;/li&gt;
&lt;li&gt;Internal business software (broad)&lt;/li&gt;
&lt;li&gt;Legacy system rebuilds&lt;/li&gt;
&lt;li&gt;Micro-services&lt;/li&gt;
&lt;li&gt;Mobile apps (too broad by itself)&lt;/li&gt;
&lt;li&gt;Realtime communication&lt;/li&gt;
&lt;li&gt;Scheduling software&lt;/li&gt;
&lt;li&gt;Startup MVPs&lt;/li&gt;
&lt;li&gt;Survey / Questionnaire software&lt;/li&gt;
&lt;li&gt;Websites (too broad by itself)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I have flagged some examples as &amp;quot;too broad by itself&amp;quot; as I feel a niche of &amp;quot;Websites&amp;quot; is not focused enough in this day and age - however if you combine it with an industry niche such as &amp;quot;Financial Websites&amp;quot; or &amp;quot;Mobile apps for the legal industry&amp;quot; then it becomes more focused.&lt;/p&gt;
&lt;h2 id=&quot;how-to-find-a-niche-that-could-work-for-your-agency-&quot;&gt;How to find a niche that could work for your agency 🧐&lt;/h2&gt;
&lt;p&gt;A niche exists whether you find it or not. You can&amp;#39;t invent a niche, they exist in the ether waiting for someone to fill them. So how can you fill them?&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Be pro-active and try to discover niches&lt;/li&gt;
&lt;li&gt;Be open to a &amp;quot;niche finding you&amp;quot;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For the best chance of success you should practise both of these.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;You gotta keep trying to find your niche and trying to fit into whatever slot that&amp;#39;s left for you&lt;/em&gt;&amp;quot; ― Dolly Parton&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;To be pro-active you should think of niche&amp;#39;s you already have some experience in, and importantly, that you can also imagine enjoying working in. I for one was never purely in this business just for the money - I also needed to have passion for my work and clients in order to get out of bed in the morning, so that is the advice I would give.&lt;/p&gt;
&lt;p&gt;To brainstorm you can run an easy discovery process, listing down the answers to the following questions so you can collate and cross reference the results:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;What industries do you already have experience in?&lt;/li&gt;
&lt;li&gt;What industries do you already have knowledge about?&lt;/li&gt;
&lt;li&gt;What industries are you interested in (and could imagine working on daily)?&lt;/li&gt;
&lt;li&gt;What types of projects are you experienced in delivering?&lt;/li&gt;
&lt;li&gt;What types of projects do you have the skills to deliver?&lt;/li&gt;
&lt;li&gt;What types of projects do you enjoy working on (and could imagine working on daily)?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Thinking about possible niches is the easy part, but trying to validate whether a niche has actual paying customers is trickier, but an important step that you shouldn&amp;#39;t ignore. If you&amp;#39;re lucky you may already have &amp;quot;insider knowledge&amp;quot; in an industry that helps you know there is a market there, or like my experience with &amp;quot;MVP&amp;#39;s for startups&amp;quot; you may have a pool of contacts you know have a problem they would pay to solve. But often you don&amp;#39;t have these insights beforehand, and instead need to do some research and validation to validate there is a market out there.&lt;/p&gt;
&lt;p&gt;One way to gain insight into a niche market is by looking for possible competition. As a starting point I recommend using our old friend Google, and try and find competitors in your niche, e.g. find other agencies that do &amp;quot;Mobile apps for the healthcare industry&amp;quot;. This will help you understand it&amp;#39;s a crowded space, or if there seem to be little or no competitors. Too crowded means you may want to get more specific with your niche, and no competition at all most likely means there is no market for it. As a rough guideline: Some competitors good, many competitors bad.&lt;/p&gt;
&lt;p&gt;Some other methods of validations are conducting &lt;a href=&quot;https://www.entrepreneur.com/article/201870?ref=devtoagency.com&quot;&gt;Keyword research&lt;/a&gt; (are people ever searching for &amp;quot;Developers for healthcare mobile apps&amp;quot; etc.) and also &lt;a href=&quot;https://medium.com/early-stage-startup-validation/how-to-setup-a-landing-page-for-validating-a-business-or-product-idea-d72c35fc012c?ref=devtoagency.com&quot;&gt;Setting up niche landing pages&lt;/a&gt; to (can you drive traffic to a very specific page to validate your concept).&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;&lt;em&gt;Look, all you can do when you find your niche is go with it&lt;/em&gt;&amp;quot; ― Vincent D&amp;#39;Onofrio, Actor&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I was lucky with my second niche as it found us, and this is also a common way of niche discovery. Be open detecting a niche has presented itself, realise it is could work for you, and then double-down your focus on it. This is one benefit of starting your agency more generalist and taking on wide variety of projects - but always being on the lookout for a niche candidate. This can also make the validation easier, as often it is a client that shows you the niche exists (by paying you!).&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If you have any thoughts, feedback, or questions (around niches or anything else!) I would love to hear from you. Please hit me up on Twitter &lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;&lt;/p&gt;
</content:encoded></item><item><title>What's your end goal?</title><link>https://www.devtoagency.com/whats-your-end-goal/</link><guid isPermaLink="false">61b29142993d27000122b489</guid><pubDate>Tue, 12 Jan 2021 07:37:39 GMT</pubDate><description>Phew, you did it. It involved some hard work, but you managed to start a software agency. Your initial fears about clients, staff, and cashflow, are all a distant memory. Congratulations your business is a success! Now, what does it look like? I want you to take some time and really think about what &quot;it&quot; is for you - it being the end goal you are heading towards. By end goal I don't mean the actual end of your business, but the destination you want to reach. &gt; &quot;To begin with the end in mind m</description><content:encoded>&lt;p&gt;Phew, you did it. It involved some hard work, but you managed to start a software agency. Your initial fears about clients, staff, and cashflow, are all a distant memory. Congratulations your business is a success!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Now, what does it look like?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I want you to take some time and really think about what &amp;quot;it&amp;quot; is for you - it being the end goal you are heading towards. By end goal I don&amp;#39;t mean the actual end of your business, but the destination you want to reach.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;To begin with the end in mind means to start with a clear understanding of your destination. It means to know where you’re going so that you better understand where you are now and so that the steps you take are always in the right direction.”&lt;/em&gt; ― Stephen R. Covey, The 7 Habits of Highly Effective People&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Whilst there&amp;#39;s a tonne of practical advice I want to share with you about starting and running a software agency (as that is the end goal of Dev to Agency!), I need to get this out of the way first.&lt;/p&gt;
&lt;p&gt;I didn&amp;#39;t set clear end goals when first starting my business, and it took 4 years for me to then figure it out the hard way.&lt;/p&gt;
&lt;h2 id=&quot;the-beginning-&quot;&gt;The beginning 📗&lt;/h2&gt;
&lt;p&gt;When I first started my custom software agency, all I wanted to do was to build interesting and technically challenging software. My co-founder and I were both freelance software engineers at the time, and we thought if we joined forces and started a company we could get bigger, more complex projects and really flex our programmer muscles. We wanted to earn a reasonable wage and work on fun things, and starting a business seemed like a great way to do it. So we did. And after close to a year of some less-than-ideal projects we finally landed a dream project. A large and complex project we could really sink our technical teeth into.&lt;/p&gt;
&lt;p&gt;That project was over a year long, and it was going great. But then some of our original clients wanted us for other projects, so we did what all businesses do - we hired our first two juniors. Six months later we had great ongoing relationships with our core clients, and still had new work coming in - so we naturally hired more developers, what a fantastic problem to have! Now with a team of 6 there was a lot more planning and management to do, so my role moved away from the technical side of things and more into management. This in turn left a hole in the development team, so we had to hire another experienced senior programmer.&lt;/p&gt;
&lt;p&gt;All these hires in a short period of time negatively affected both the quality of our work and our delivery timelines (as at that stage we did not have great standards and processes in place), so my co-founder moved into a CTO role to oversee the tech team, and we hired a new project manager to make sure things got done well and on time. At this point we realised we needed to pay for a sales and marketing team to win more work - as our payroll had increased to 6-figures per month. Needing to bring in that much money meant we couldn&amp;#39;t always work on interesting and technically challenging projects, so some less-than-ideal projects had to be taken just to keep the money coming in. I think you see the pattern. Before we knew it we were 10 people and still hiring. I know ten people isn&amp;#39;t huge by any means, but we now spent a lot more money, which meant we needed to earn a lot more money. And frankly, we didn&amp;#39;t know when to stop.&lt;/p&gt;
&lt;h2 id=&quot;how-did-i-get-here-&quot;&gt;How did I get here? ⚠️&lt;/h2&gt;
&lt;p&gt;It crept up slowly over a few months, and then it hit me hard. I realised was unhappy. Externally I felt a success, I mean we had a big office and shiny new things to fill it with, we had built something from the ground up (that was still growing), and our clients were generally happy. But I didn&amp;#39;t know where it was going, where I was going, where we actually wanted to go.&lt;br&gt;I wasn&amp;#39;t &amp;quot;coding interesting and technically challenging software&amp;quot; like I originally wanted, in fact I was no longer really an software engineer at all - but a stressed out manager who worked too much.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“If you don’t know where you are going, you’ll end up someplace else.”&lt;/em&gt; ― Yogi Berra, former New York Yankees catcher&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;After many conversations we decided we needed to make a change - we had to stop growing for the sake of growing, and instead focus and simplify. This meant dealing with a few uncomfortable truths: we had to fire the clients that didn&amp;#39;t align with the work we wanted, and heartbreakingly we had to let some staff go to reduce our payroll. My co-founder also decided he wanted to leave the business - basically it was just a shit time. But I had let it happen. We had let it happen because we never had an end goal, we just kept on moving along, hiring more staff, winning more projects, hiring more staff - an endless loop. We let other forces control our destiny - and looking back its obvious why we hit a tipping point.&lt;/p&gt;
&lt;h2 id=&quot;realignment-&quot;&gt;Realignment 🧘&lt;/h2&gt;
&lt;p&gt;Although it felt 4 years too late, I was forced to think really hard about what I personally wanted out of my business. What I wanted for my staff and clients, and what my end goal was.&lt;/p&gt;
&lt;p&gt;I decided that day-to-day I needed to stay technical, and for my sanity, code at least a couple of times a week. I wanted to be the technical lead but also scope new projects and do client pitches (as strangely by then I actually enjoyed pitching!). I wanted to only take projects that were a good fit for us, and I wanted the team to be excited by our new projects, not bored. I wanted to never sacrifice on project quality again, and I wanted clients to be blown away by the quality of our work.&lt;br&gt;I didn&amp;#39;t want to work too much, ideally no more than 38 hours per week (and never on weekends), I wanted the team to have a good work-life-balance, and for them to feel supported and valued. I wanted to stay small - a small amount of great staff, a small amount of great clients. I wanted everyone in the business to be paid very well (including myself) - and lastly, I realised I did not want to run this business until the day I died. I knew that at some stage in the distant future I would want to do something new.&lt;/p&gt;
&lt;h2 id=&quot;a-phoenix-from-the-ashes-&quot;&gt;A phoenix from the ashes 🔥&lt;/h2&gt;
&lt;p&gt;Having an end goal helped me regain control of my business. It no longer felt like a distant dream, but an achievable destination - and that helped me design a roadmap on how to get there.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“I ain’t Martin Luther King. I don’t need a dream. I have a plan.” ― Spike Lee&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I realised we couldn&amp;#39;t have a team of junior programmers - or just specialists in either frontend or backend - we needed full-stack developers who were mature, experienced, self-motivated enough to lead a project, and personable enough to work well within a team. Instead of taking every project that came through the door I needed to focus on a niche - this helped me double-down on custom internal business software, usually for boring businesses (that made money) and had some archaic internal workflows that needed automation.&lt;/p&gt;
&lt;p&gt;As internal software is so integral to the business, this forced us to have a larger focus on high quality, bringing in stringent code reviews, automated testing, and the technical standards and processes to make sure the quality always remained high. I rebranded our website and communications to reflect our focus, and took down all our past work that didn&amp;#39;t align with the goal. We gave the remaining team a great pay-rise (including myself), and importantly brought in regular one-on-one chats between myself and the individual team members, so I could make sure they always had time to talk to me directly about whatever was one their mind, and I had time to be transparent and open about our business. With such a lean team, it&amp;#39;s all about the staff and their happiness, so I tried as hard as I could to give them everything they needed in order to do great work.&lt;/p&gt;
&lt;p&gt;Lastly, as I knew this business was not something I wanted to do until retirement, I took steps to avoid vendor lock-in for our clients by using only tried and tested technologies, and having detailed documentation (both technical and functional) for any handover needed. I also made sure to keep up relationships with individuals and other companies that could possibly be interested in acquiring the business in the future - just to keep those doors open.&lt;/p&gt;
&lt;p&gt;This new reincarnation of the business was a breath of fresh air. Over the next four years we produced the best work ever. With a team half the size we managed to deliver larger and more technical projects at a higher quality than before. This strengthened the relationships between us and our smaller client base - and generally it was a &amp;quot;happier&amp;quot; place to work than the business of four years prior.&lt;/p&gt;
&lt;p&gt;This end goal brought with it closer clients, more ongoing work, happier staff, and a higher quality output. This in turn directly lead to an acquisition offer in 2020 from a larger agency. Although selling the business was not a huge priority at the time, it was too greater opportunity to pass up, and it aligned with the end goal I had set years earlier.&lt;/p&gt;
&lt;h2 id=&quot;what-is-your-end-goal-&quot;&gt;What is your end goal 🎯&lt;/h2&gt;
&lt;p&gt;So before you purchase your domain and print your business cards - I recommend you take the time to think this through, and plan your ideal end goal for your business. Imagine you have &amp;quot;made it&amp;quot;, you have all the work you want and great staff to do that work...&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;What does day-to-day look like, what do you do exactly?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What don&amp;#39;t you want to do?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;How many hours do you work per week?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;How many staff members do you have?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Are your clients local (you meet face-to-face), global - or both?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What types of projects do you focus on (or does your agency do everything)?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;How much money do you personally want to make per year?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;How long do you want to run your agency for (is this a forever endeavour?)&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;p&gt;In retrospect having an end goal is pretty darn obvious, but sometimes you get so wrapped up in the idea of starting a business that you forget about the obvious things. I wish someone could have told the younger me this story - and I hope my story helps at least one other person.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;“Just because you made a good plan, doesn’t mean that’s what’s gonna happen.” ―Taylor Swift&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Of course, the best laid plans can still fail. And I am taking a bit of creative license in my retelling, as even after our &amp;quot;reincarnation&amp;quot; we still had to tweak our plan every so often to make sure we were on the right track to our end goal.&lt;br&gt;And along with this you also want to periodically review your end goal. Things change, we grow as we learn, and this leads to goals morphing and evolving. But having a &amp;quot;north star&amp;quot; that you can always look at and ask yourself &amp;quot;Am I heading towards my goal?&amp;quot; - that is never a bad thing to have.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If you have any thoughts, feedback, or stories of your own I would love to hear from you. Please hit me up on Twitter &lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;&lt;/p&gt;
</content:encoded></item><item><title>You are the gold standard</title><link>https://www.devtoagency.com/you-are-the-gold-standard/</link><guid isPermaLink="false">61b29142993d27000122b488</guid><pubDate>Tue, 05 Jan 2021 04:40:00 GMT</pubDate><description>The gold standard is the measure by which everything else is measured, and when starting a small software agency - or in fact any small business where the owner is also at the coalface of where shit gets done - you have the opportunity of setting the gold standard of what's expected. The quality that is expected, the communication that is expected, the client respect that is expected. You are walking-the-walk as opposed to just talking-the-talk - and this is a superpower of the small that shoul</description><content:encoded>&lt;p&gt;The gold standard is the measure by which everything else is measured, and when starting a small software agency - or in fact any small business where the owner is also at the coalface of where shit gets done - you have the opportunity of setting the gold standard of what&amp;#39;s expected.&lt;/p&gt;
&lt;p&gt;The quality that is expected, the communication that is expected, the client respect that is expected. You are walking-the-walk as opposed to just talking-the-talk - and this is a superpower of the small that should be used to your advantage.&lt;/p&gt;
&lt;h2 id=&quot;the-owner-maker-standard-&quot;&gt;The owner/maker standard🥇&lt;/h2&gt;
&lt;p&gt;In all the businesses I have started I have been both the owner and the maker. I don&amp;#39;t think my software agency would have been as successful otherwise, especially in those early years. Being an owner/maker puts you in the unique position of being able to design and implement the standards you want for your business, but also be able to personally practise them day-to-day and lead by example. Being a boss and a builder also creates a smaller feedback loop, allowing for quicker detection of standards and processes that need tweaking - which means moving faster towards higher quality.&lt;/p&gt;
&lt;p&gt;You directly impact your business, you are on the front line. Your not just sitting behind a large desk 6 floors above the code-monkeys who are writing the software - you are both a CEO and code-monkey. (I hate that term, mental note: never say &amp;quot;code monkey&amp;quot; again). Upper management does not need to authorise your decisions, and there isn&amp;#39;t a committee and multiple meetings required to agree on an approved strategy - there is just you, and this is a strength.&lt;/p&gt;
&lt;h2 id=&quot;what-should-i-standardise-&quot;&gt;What should I standardise? 📚&lt;/h2&gt;
&lt;p&gt;First of all, you don&amp;#39;t need to go over the top with policies and procedures for everything, that sounds like a big company - and I&amp;#39;m all about embracing your small company specialities.&lt;/p&gt;
&lt;p&gt;When you&amp;#39;re starting out your business is an extension of you - and you will inevitably implement standards and practises based on what you value. These don&amp;#39;t need to be etched into a stone tablet or framed above your desk - to be honest I don&amp;#39;t really care if you write them down or not. But your business standards should be communicated clearly and consistently to your clients and your team, and you are the best to communicate this.&lt;/p&gt;
&lt;p&gt;This will differ from person-to-person, but some standards that are important to me are;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Project quality →This includes the software quality, but also that the solution actually nailed the problem, and the quality of client-vendor understanding was high.&lt;/li&gt;
&lt;li&gt;Client relationships → How the business interacts with clients from first contact, during a project, and long after a project is delivered.&lt;/li&gt;
&lt;li&gt;Teamwork → What is expected from your team and how they should help those around them.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;standardise-you-&quot;&gt;Standardise you 🤟&lt;/h2&gt;
&lt;p&gt;By default, as the owner of a small business many of your own personality traits will become your business standards. For example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Curious → Create a culture of questioning and knowledge sharing&lt;/li&gt;
&lt;li&gt;Empathetic → Ensure clients understand that you understand their problem&lt;/li&gt;
&lt;li&gt;Friendly → Design a welcoming client onboarding flow&lt;/li&gt;
&lt;li&gt;Honest → Make sure clients have a clear understanding of costs&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Positive traits are easier as they almost just happen by default, but it&amp;#39;s important to also study your traits which do not always seem so positive, and flip them on their head to become positive standards in your business (and hopefully in your life). For example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Anxious → Ensure your business always has adequate runway in the bank account&lt;/li&gt;
&lt;li&gt;Forgetful → Create a culture of documentation&lt;/li&gt;
&lt;li&gt;Lazy → Create a culture of automation&lt;/li&gt;
&lt;li&gt;Negative → Help clients understand other options and alternatives&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;that-s-a-lot-of-pressure-&quot;&gt;That&amp;#39;s a lot of pressure 😳&lt;/h2&gt;
&lt;p&gt;Whilst it&amp;#39;s important to set the gold standard as an owner/maker - this does not mean you needs to have every answer to every question.&lt;/p&gt;
&lt;p&gt;As the Peter Parker principle states &amp;quot;With great power comes great responsibility&amp;quot;, and it&amp;#39;s true, you have a lot of power as the owner of your business. But you are not perfect, you are human - you will learn, improve, evolve, and tweak as you go along. Another big benefit of being small is that you can change easily, so use that to your advantage.&lt;/p&gt;
&lt;h2 id=&quot;laying-a-foundation-of-standards-&quot;&gt;Laying a foundation of standards 🏠&lt;/h2&gt;
&lt;p&gt;There will be a time where your maker responsibilities take a back set to your owner responsibilities - but I believe to set the gold standard of how your business runs, being an owner/maker in those initial formative years is integral. You have then put in place the guidebook to ensure everyone knows what&amp;#39;s expected, and as new team members join or new clients get signed on - there is consistency.&lt;/p&gt;
&lt;p&gt;For my software agency I stepped away from daily coding after a few years, but by then we had strong standards along with checks-and-balances in place to ensure quality. Even though I was not programming anymore, I still kept and eye on our standards with daily code reviews, software architecture design chats with the team, and getting down-and-dirty with some quality assurance testing every so often.&lt;/p&gt;
</content:encoded></item><item><title>My small custom software development agency</title><link>https://www.devtoagency.com/my-small-custom-software-development-agency/</link><guid isPermaLink="false">61b29142993d27000122b487</guid><pubDate>Tue, 29 Dec 2020 01:24:28 GMT</pubDate><description>I want Dev to Agency to be a place where software developers who are interested in starting a software development agency (or have already), can learn from some practical examples around how I started, ran, and ultimately sold my agency after 8 successful years. Perhaps I am secretly writing this for my younger self, as this something I found hard to find good information on when starting out in 2012. To get slightly side-tracked for a second, I kind of hate the word &quot;agency&quot;. I prefer to cal</description><content:encoded>&lt;p&gt;I want Dev to Agency to be a place where software developers who are interested in starting a software development agency (or have already), can learn from some practical examples around how I started, ran, and ultimately sold my agency after 8 successful years.&lt;/p&gt;
&lt;p&gt;Perhaps I am secretly writing this for my younger self, as this something I found hard to find good information on when starting out in 2012.&lt;/p&gt;
&lt;p&gt;To get slightly side-tracked for a second, I kind of hate the word &amp;quot;agency&amp;quot;. I prefer to call my business a &amp;quot;software development consultancy&amp;quot;, but that was really me just not liking the word agency. At the end of we did client service work for businesses and individuals - and that&amp;#39;s an agency. That is kind of not related to this post - but I just wanted to get it off my chest. Now let&amp;#39;s move on.&lt;/p&gt;
&lt;p&gt;An &amp;quot;agency&amp;quot; can take many different forms, on one end of the spectrum we might have a 150 employee full-service digital agency offering everything from communication and branding, web development, to SEO optimisation, and then  on the other end of the spectrum we may have one single person who does &amp;quot;Wordpress&amp;quot; (that is, they configure various plugins) - so I want to give an overview of the software development agency I built, so you can then ascertain if these words can benefit you.&lt;/p&gt;
&lt;p&gt;I feel compelled to write this post as I don&amp;#39;t want to be misconstrued as someone who can &amp;quot;Turn your small software agency into a billion dollar money printing making business in 14-days!&amp;quot; - that&amp;#39;s very much not me, and very much the type of content I was wary of when starting out. Instead I want to talk about the key-values and strengths that I focused on at my agency - values which I believe helped my business succeed.&lt;/p&gt;
&lt;h2 id=&quot;1-small&quot;&gt;1. Small&lt;/h2&gt;
&lt;p&gt;My natural instinct is to be small and stay lean. These traits are not mutually exclusive, however to me they are cornerstones of the business I built. On average we were 5 people, this number went up and down, but for the majority of years it was 5 people - all full-stack software developers, and in the later years one dedicated account &amp;amp; project manager. Small can mean a lot of things, but to me it means the entire team working closely together, and as a leader - having time to truely understand and support each team member on each individual level. Compared to larger businesses, a reduced monthly payroll can allow you to only take projects that play to your strengths, and having a smaller number of staff to pay - may actually mean you can pay higher wages than the industry standard. Being small helped stay lean, and thinking lean helped zoom in and ignore things that are extraneous or unneeded. This can mean not spending money on the new shiny SaaS tools of the month, and it can mean working out of a small(er) shared space, as opposed to a large office that perhaps could seem more impressive to clients. Whilst I have no experience building a large agency with many teams and departments, I do have experience building a small cross-functional team, producing high output at high quality.&lt;/p&gt;
&lt;h2 id=&quot;2-custom-software&quot;&gt;2. Custom software&lt;/h2&gt;
&lt;p&gt;My business did not build websites or software you could buy or download off-the-shelf, but we created tailor-made software - designed, architected, developed and deployed to meet the exact needs of the client. Possible categories of custom software include business-to-business software for businesses to sell on to other businesses (B2B), business-to-consumer software for a business to sell to the general public (B2C) - and another category is internal software, that is software that the businesses need to run themselves internally. It&amp;#39;s the last category (internal software) that interested me the most, as all businesses end up with complex processes and workflows that are in need of automation, and they don&amp;#39;t need to be billion dollar businesses to realise a small improvement to the process can return large results. I use the term &amp;quot;boring businesses&amp;quot; to describe my ideal client, and where this type of software can work well. For example, a 30-year family owned company called &amp;quot;H&amp;amp;R Widgets&amp;quot; that make and deliver &amp;quot;widgets&amp;quot; for other boring businesses. You would never hear of or notice this company in your day-to-day life, but they can be making millions per year in profit, and using a highly manual internal process using hundreds of paper based forms, shared spreadsheets with many macros and flaky integrations the owners cousin built in &amp;quot;VB script&amp;quot; in 1997. This is a perfect client.&lt;/p&gt;
&lt;h2 id=&quot;3-long-term-client-relationships&quot;&gt;3. Long-term client relationships&lt;/h2&gt;
&lt;p&gt;I feel it is a misconception that most important step in building custom software is the software itself (the end result) - where I feel it is instead really understanding the business and the specific problem area the solution is addressing. Without a strong understanding of the problem and business goals, you risk wasting time, money, and reputation building the wrong thing. These client relationships need to  be built on a foundation of &amp;quot;a partner in problem solving&amp;quot; rather than just &amp;quot;a vendor that will deliver the new widget workflow software&amp;quot;. This starts before the project begins, and continues long past the project is delivered. Being a partner and not just a vendor allows you to understand other areas of the business, which will often lead to further conversations and opportunities. After you have delivered a bespoke solution for a client, no-one else on earth knows this exact software better than your team. Even though thorough documentation is paramount for training and up-skilling new hires - this fact puts your business in a good position, and whilst you should not take advantage of this responsibility - it does mean that it&amp;#39;s in the best interest of &amp;quot;H&amp;amp;R Widgets&amp;quot; to keep a good ongoing relationship with you also.&lt;/p&gt;
&lt;h2 id=&quot;4-quality&quot;&gt;4. Quality&lt;/h2&gt;
&lt;p&gt;As the custom software is integral to the client&amp;#39;s business - it cannot just &amp;quot;go down&amp;quot; every couple of weeks, and as the technical partner &amp;amp; problem solver it is your responsibility to ensure the checks and balances in place for high quality in all areas. Quality in all areas starts with making sure you have a thorough understanding of the business and the problem area to guarantee the quality of the project goals, that the software you write is high-quality and built to last to ensure quality of the code, and that the project management and delivery processes that you put in place (including user testing and sign-off) are clearly understood and formalised - to ensure the overall project quality. All of these points are hard in their own way, but as you are building relationships and software that will be sticking with you for the long term, by not focusing on quality, you are shooting yourself in the foot by paving a tough road ahead. Over the 8 years I ran my agency our quality was the most common praise we received from clients, and often amazement that a small team can produce such results.&lt;/p&gt;
&lt;h2 id=&quot;5-staff-happiness&quot;&gt;5. Staff happiness&lt;/h2&gt;
&lt;p&gt;Small can also be hard, people are not replaceable without losing a lot of knowledge, and working on custom software often requires deep understanding of complex business rules. I&amp;#39;m confident that if my staff had of left after just one or two years, then I would have really struggled to keep my business running - and could not have achieved the same level of success. There is always the random &amp;quot;Bus Factor&amp;quot; that needs to be taken into account (a team member being hit by a bus), but otherwise I believe the main focus should be on happiness of employees and making certain they are getting everything they need to be as happy as they can be at work. For me this meant building a very close team, a team that had fun, but a team that worked hard. Staff that understand the values of your business, and understand that in a small team they will have a large impact. It&amp;#39;s not always glamorous working on projects for boring businesses, but the happiness and purpose does not need to come from the project itself - but from creating great code with teammates, always learning, and knowing you are not on your own - that people will always have your back when you need it.  &lt;/p&gt;
&lt;p&gt;This post covers a lot of points I plan on digging deeper into in the future, unpacking each of these points in more detail and some more examples. If this is something that interests you simply subscribe below, and you will recieve all new posts by email.&lt;/p&gt;
</content:encoded></item><item><title>About Dev to Agency</title><link>https://www.devtoagency.com/about/</link><guid isPermaLink="false">61b29142993d27000122b485</guid><pubDate>Mon, 28 Dec 2020 00:47:00 GMT</pubDate><description>I started Dev to Agency to help developers start and run successful software development agencies. Focusing on full-stack developers with small agencies (&lt;= 10 people), building high quality custom software for clients.</description><content:encoded>&lt;figure class=&quot;kg-card kg-image-card&quot;&gt;&lt;img class=&quot;kg-image&quot; loading=&quot;lazy&quot; src=&quot;https://www.devtoagency.com/content/images/2021/12/chris-alpha-round.png&quot; alt=&quot;&quot;&gt;&lt;/figure&gt;
&lt;p&gt;👋 Hi, I&amp;#39;m Chris (&lt;a href=&quot;https://twitter.com/chrisrickard?ref=devtoagency.com&quot;&gt;@chrisrickard&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;To be honest I never thought I would start an agency. I was full-stack software developer, not a CEO. But through a series of random events, in 2012 I decided to start a small agency focusing on building high quality custom software for clients - and it has been one of the best things I have done in my life.&lt;/p&gt;
&lt;p&gt;I developed a niche building custom internal tools for what I like to call &amp;quot;boring businesses&amp;quot; - which allowed us to focus on our target market, and stop pitching for every project that came along.&lt;/p&gt;
&lt;p&gt;In 2020 my agency was acquired (by a larger agency), and it gave me time to reflect on the processes and strategies I learnt along the way. After 8 years of running my business I learnt how a small group of technically focused people can&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Punch above your weight 🥊&lt;/strong&gt;&lt;br&gt;Winning large projects when competing with companies 10 to 20 time as large.  &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Build client relationships that last for years 🤝&lt;/strong&gt;&lt;br&gt;Having a smaller amount of larger clients, rather than a larger amount of smaller clients.  &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Keep software developers happy and engaged 🥰&lt;/strong&gt;&lt;br&gt;Relationships with staff and clients are key. Without them an agency is just a logo.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Dev to Agency is my outlet for sharing what I have learnt, as I found it hard to find trustworthy advice online, I am hoping to &amp;quot;give back&amp;quot;, and help some people along their path.&lt;/p&gt;
</content:encoded></item></channel></rss>
