Setsumei / local product evaluation

Discuss a Setsumei evaluation

Tell us what your team needs to understand: an unfamiliar codebase, a consequential change, recurring code risk or a coding-agent workflow. We’ll discuss fit and a local evaluation built around one question.

Discuss an evaluation Review the technical method

Start with a high-level description. Do not send source code, credentials, or security findings by email.

Contact Syntaxa

Talk through the question and the next step.

A high-level question is enough to start. Discuss how your team would use the scan, browser brief or MCP queries, then agree the evaluation scope and commercial terms.

Request by email: hello@syntaxa.ai How local deployment works

Prepare a detailed inquiry for email

Draft your message

The evaluation

What your team will evaluate.

Choose one question to test the product’s fit for recurring work. Evaluate the usefulness of the analysis, whether the results are inspectable, and how practical it is to refresh and reuse them.

What to inspect

Inspect the analysis and use its outputs.

Structure and codebase orientation Components, dependencies, communities, importance, coverage and unresolved relationships from analyzed source.

Prioritized candidate findings Security, performance, reliability and structural candidates with source context. Investigation outcomes appear where optional investigation ran.

A local browser scan brief Open the generated HTML in your browser to explore the current GUI. Use reports and architecture documentation for the relevant task.

Reusable context and agent queries Where configured, use read-only MCP to query stored analysis. Refresh after changes and inspect freshness before the next task.

The first conversation

Agree what a useful evaluation would answer.

Discuss the result your team needs and how you would judge it. Source/build details and relevant participants help plan the work; they are not prerequisites for an inquiry.

Did the results help answer the chosen question?
Could engineers inspect important relationships and unknowns?
Was setup, analysis refresh and reuse practical for the team?

Commercial terms and compatibility

Agree on the software fit and evaluation terms.

Agree software fit, local prerequisites, evaluation scope, price, and schedule in written commercial terms before committing.