In this paper we see that the best way to build a co-verification methodology for SoC verification is to combine a single platform that provides logic simulation, simulation acceleration, and in-circuit emulation with application specific solutions for co-verification and transaction-based verification. Furthermore, we see that combining many point tools to try to complete the methodology is not good enough because the tools will not work well together. Interoperability between the platform and the application of transactionbased verification and HW/SW co-verification is essential to work smarter, not harder. Additionally, transactions and simulation timestamps are the communication method for hardware and software teams to effectively pinpoint the exact cause, time and location of problems as well as provide a standalone test case to replicate the problem within each environment. Along the way we also learn some useful information about co-verification methods and the ARM architecture.