Scopic started from a specific frustration. The map you draw to understand a problem and the database you keep to track it always diverge. One has the structure. The other has the detail. You build both, maintain both, and they never quite say the same thing.

The tool we wanted was one where the map and the database are the same thing — where placing two elements next to each other and drawing a line between them is also entering a row in a database. Where the line itself has a name, a type, and properties of its own. Where you can look at your work spatially and interrogate it structurally without switching tools.

The deeper problem is the relationship. Most tools let you organise things. None of them treat the connection between things as something worth tracking. Who funds what. What challenges what. What is a prerequisite for what. These relationships are often the actual research, the actual knowledge, the actual work. They live in your head or in a footnote.

Scopic is built around the idea that the connection between two things is as important as the things themselves — and that it should be as easy to name, describe, filter, and open as any other record in your database.

The name comes from skopein — the Greek word for looking, observing, watching. It names a mode of seeing, not a domain. Scopic does not assume you are a researcher or a consultant or a founder. It assumes you are someone with something to figure out, and that a map might help.

We are building it in early access. The product is early. The idea is not.

Questions or thoughts: support@scopic.app