About Us

Company

About Schwaps

Schwaps LLC designs, develops, and operates specialized software systems for organizations managing property-tax appeals, assessment data, valuation review, evidence, and related professional workflows.

Our work is built around a straightforward principle: important operating processes should not depend on disconnected spreadsheets, inboxes, PDFs, and legacy databases when a structured system can make the work clearer, more reviewable, and more controlled.

Focused operating domain

Built around consequential property-tax work.

Schwaps concentrates on workflows where data quality, deadlines, review discipline, and reliable records matter.

  • Property-tax appeal operations
  • Assessment and valuation data systems
  • Portfolio review and opportunity screening
  • Evidence and report preparation
  • Internal dashboards and client-facing portals
  • Custom operational software

We do not approach software as a collection of isolated features. We design around the users, data, decisions, controls, and outputs that the operating process must support.

Flagship platform

AppealZoo® and Schwaps

AppealZoo® is a property-tax technology platform operated by Schwaps LLC. It brings property analysis, evidence development, workflow, and portfolio oversight into one controlled working environment for property-tax professionals.

Product capabilities, workflow demonstrations, implementation information, and enterprise briefing requests are available at AppealZoo.com.

What Schwaps builds

Infrastructure shaped around the operation.

Schwaps works with organizations that have a valuable internal process, meaningful operating volume, and no acceptable off-the-shelf solution.

Custom application development

Purpose-built software for operating processes that require a specialized working environment.

Data architecture and database design

Structured data systems for property, assessment, portfolio, matter, and workflow information.

Workflow automation and reporting

Operating paths that replace fragmented spreadsheet, inbox, PDF, and legacy-database processes.

Portfolio and property intelligence

Working environments for organizing and reviewing property and portfolio information.

Evidence and document-production infrastructure

Tools for developing, organizing, reviewing, and producing structured supporting materials.

Product, implementation, and operating architecture

Support for defining requirements, structuring operating models, validating workflows, and introducing software into active organizations.

Engagements

How engagements begin.

An engagement begins with the operation itself: how work currently moves, where information breaks down, who makes decisions, what must be reviewed, and what records or outputs the system must produce.

  1. 01 — Operating workflow assessment

    Establish the process, users, decisions, constraints, and outcomes the system must support.

  2. 02 — Requirements and data review

    Review how work moves, where information breaks down, and what records or outputs are required.

  3. 03 — Scope and system architecture

    Define the system boundary, data structure, implementation approach, and validation plan.

  4. 04 — Build and validation

    Develop the agreed system and test it against representative work before broader use.

  5. 05 — Implementation and adoption

    Introduce the approved operating path and document the responsibilities relevant to the engagement.

The proposed scope should be documented around the actual operating environment rather than inferred from general website language.

Justin B. McClelland
Justin B. McClelland Founder, Schwaps LLC

Leadership and accountability

Specialized work with identifiable responsibility.

Schwaps is led by Justin B. McClelland, whose work spans property-tax analysis, software architecture, data systems, workflow design, and product development.

Justin’s research, advisory work, visual analytics, and public property-tax analysis are presented separately at JustinMcClelland.com.

Visit JustinMcClelland.com

Contact

Have an operating process that should become software?

Start with a focused discussion about the workflow, data, users, decisions, controls, and outputs the system must support.