We focus on researching & developing game-changing technology — particularly: database, market, and information problems/solutions with far-reaching global effects.
Every David needs a Goliath. We need big, interesting challenges to tackle. Without interesting challenges we're just a bunch of smart people discussing cool ideas and tech—fun but not useful. If you have an interesting challenge— throw it at us and we'll start figuring out possible solutions. Is the problem big enough, complex enough, valuable enough, and solvable? We're interested in these things.
Is the challenge economically worth solving? Are people willing to pay for it--who? How can it be implemented? How will we get the solution to these customers? Is our solution worth the cost of development and risk? Is it possible for us to implement the solution using accessible resources? Can we develop a solution within a useful timeframe? What are the risks to our plans?
There is no use building a latter leaning against the wrong wall. Are we hitting the 'sweet-spot' of our customers' needs? What features do we need to implement? What is a 'minimum viable product' people will buy/use? We usually spend a lot of time here speaking to various customers, getting useful feedback, and verifying we aren't just fooling ourselves.
You can draw something on paper--but can you build it? Here we execue our plans and organize the resources to construct our solution--frequently going back to re-validate our model. There are plenty of challenges to solve here as we iteratively engineer, build, and assess our production plans with customers and test solutions and their real-world feasibility.
If we've done all of the other steps properly this step is not trivial but is fairly easy to execute with the right people, resources, and methods in place. If we've messed up somewhere else then this can be challenging. This step is usually where the product developers and other stakeholders see the payoff for all their efforts.