How it works

Bring the research, relationships, and geography into the same place.

SC.Community is a local Windows application for building a useful CRE working system from the information you already collect.

1. Prepare a source

Review the structure before it becomes a record.

Start with an XLSX, CSV, JSON, or KML source. Preview the fields, map each source value to the record field it belongs in, and commit the records deliberately. PDF and email information need preparation or a user-selected external tool before they become structured records. That preparation step helps a one-off research file become information you can find again.

It is closer to setting up a useful game engine than filling out a fixed template: the engine provides the pieces and rules, while your data model defines the world and work that matter to you. The same prepared comps can then appear on a map, in a List, and in a private tool without being entered again.

2. Connect the context

Keep a property attached to the people, fields, and work around it.

Relationships make the link between contacts, companies, properties, locations, and activities explicit. Classifications and custom fields give existing records the typed values your work requires; they do not create new native entity types. A derived value uses exactly two same-record numeric operands and one arithmetic operation, not a full spreadsheet formula engine.

The result is not a generic pipeline. It is a local record system that preserves why a person, place, note, or next step belongs to the same question.

3. Use the context that fits the question

See geography, attached work, and reusable working sets from the same records.

Geographic context: Use Locations and spatial criteria to find records, then work with Shapes and Layers when geography is part of the question.
Reusable working sets: Keep Saved Search criteria separate from a deliberate reviewed List, then return to either view when the work resumes.
Attached work: Use Activities and Calendar to attach notes, follow-ups, and scheduled work to the records involved so the next step stays in context.

4. Preserve document context

Keep the connection without pretending every file is the database.

Document records link the file’s business context to the properties, people, activities, and Lists that explain its use. When a template needs selected record values, those values are bound separately for an SC.Artifacts template. SC.Community owns the business context; SC.Artifacts is the separate boundary for file bytes, rendering, templates, provenance, and generation.

That distinction keeps a source document useful without treating every file as automatically ingested or generating a hidden pipeline around it.

5. Reuse outside the application

A local foundation you can inspect and extend.

While Desktop runs, the installed application exposes a documented local API that uses the same local PostgreSQL/PostGIS data, alongside OpenAPI documentation, a portable skill, and in-product Help. Private external tools and agents are optional and subject to the applicable license; no embedded assistant is required to use SC.Community.

Download SC.Community Early Access Read why Space Connect is building it