1. Lay out the problems caused by the current architecture. Not in developer terms like "tightly coupled" but rather in terms managers will understand - the rea

1. Lay out the problems caused by the current architecture. Not in developer terms like "tightly coupled" but rather in terms managers will understand - the real cost per client. Prove that a cleaner architecture will lead to faster turnaround and therefore reduce the overheads - leading to more clients and/or higher profits. 2. Design a cleaner architecture. Look at current and possible requirements. Maybe not too much detail, but perhaps a basic database schema, class designs, etc (whatever is appropriate to your language/framework). 3. If you are using MS tools, read up on the lastest developments there - ASP.NET MVC for example - and show how using new tools would improve the design. 4. Perhaps get yourself involved more in the management side of things. Learn more about the business as a whole, why decisions are made. That will make you sound more informed on the technical side as well. If all else fails, then look for another job by all means - but bear in mind that the situation you describe is all too common in non-technical lead companies. In an ideal world, the business-savvy techies would be in charge (and those that are - Google, Gates-era Microsoft, etc - they are) but those companies are few and far between. If you are otherwise happy at the company then perhaps start a side-project - commercial or open-source - to keep your skills fresh, so you'll be in a better position for your next job.