Here is one (a bit more complex) Excel addin you can look at. The author describes how he organized his solution into different projects and I agree with most of his decisions. He separates the domain logic from the user interface / excel and also adds unit testing project and one project that bootstraps his whole addin:
http://www.clear-lines.com/blog/post/VSTO-solution-organization.aspx
Source code is available here: http://vstostocks.codeplex.com/
This is a VSTO solution but you can easily apply the same principles to a plain COM addin. It also quite similar to your project.
It is hard to give guidelines without knowing specifics of you problem. I think if you stick to main guidelines when it comes to OO design like SOLID, writing clean code, you should be just fine.