What the name does - and does not - identify
The public descriptions point to a possible Pennsylvania publishing-software organization: they provide a location, industry focus, product descriptions, and a reported ownership history to test against current records.
The practical conclusion is narrow. You can investigate a Pennsylvania publishing-software organization that matches the name, but you should not treat the match as confirmed merely because several directories use the same wording. The organization’s current registration status, registered address, and contracting authority remain unconfirmed, as does whether all descriptions refer to the same legal entity.
Use the reported details as matching fields rather than as a completed company record:
- Compare the exact legal name and jurisdiction, including punctuation and the LLC designation.
- Match the reported Bethlehem, Pennsylvania location and publishing-software focus against an official registration record.
- Reconcile the ownership, leadership, website, services, and contact details before discussing a project.
- Keep directory estimates and attributed descriptions separate from facts confirmed by an official filing or direct organizational contact.
That distinction protects your decision from a common error: treating a recognizable name as if it were a verified provider identity.
The strongest available identity lead is a Pennsylvania publishing-software company
The directory description associates the name with Bethlehem, Pennsylvania and publishing workflows, but it does not confirm the legal entity. The location should therefore be checked against an official filing and a current business contact.
RocketReach lists SIC codes 737 and 73 for Software Consulting Services LLC. Those codes are classification entries displayed by a third-party directory; they do not, by themselves, establish the services the organization currently sells or the legal entity behind the listing. RocketReach also lists NAICS codes 541, 541511, 54, 5415, and 54151. Treat both code sets as search aids, not as a substitute for a registration record or a direct capability discussion.
LeadIQ lists the largest employee groups by country as the United States at 86%, South Africa at 10%, and India at 3% of the country-distributed employee profiles it lists. The percentages describe that directory’s profile distribution, not a verified workforce census, and the rounded values do not establish where every employee or contractor works. They may still help you test whether a contact, domain, and stated operating footprint are consistent with the profile.
Taken together, Bethlehem, Pennsylvania, publishing-workflow software, and the listed industry classifications form a useful identity pattern. They do not answer the decisive question: whether the organization you find in an official record is the same organization represented by the directories.
What Software Consulting Services LLC reportedly provides
The reported customer group ranges from small community publishers to large metropolitan organizations. This points to a specialized publishing-software profile rather than a general-purpose software consultancy, although you still need to confirm the current service scope before treating it as a fit.
The reported offering includes several distinct components:
- A Community Advertising System is described as a managed service that integrates advertising and production workflows for community newspapers for a predictable monthly fee.
- Individual software modules can be deployed independently or integrated with third-party systems.
- Software Consulting Services LLC is described as reselling and supporting FotoWare Digital Asset Management solutions for large asset collections and varied publishing workflows.
Software Consulting Services LLC says its software is used daily at over 300 physical locations and supports the production of more than 2,000 publications across 12 countries. The 300 figure measures physical locations, the more-than-2,000 figure measures publications, and the 12-country figure describes the stated international footprint. These are company-associated scale statements, not independently established deployment totals.
A 2022 press release describes the business as a small to mid-sized software development company with a model based on a substantive upfront software purchase followed by ongoing technical support. That description dates from 2022, so you should not assume that the commercial model remains unchanged in 2026.
The reported history also traces the organization to a 1975 founding by Martha and Richard Cichelli, who were software developers focused on publishers’ evolving needs. LeadIQ estimates about 41 employees across 3 continents, with most of those estimated employees in North America. The employee figure is a directory estimate and belongs in the same provisional category as the other third-party workforce figures.
For an initial provider assessment, ask for the current product list, implementation responsibilities, support terms, integration boundaries, pricing model, and customer reference policy. The company’s reported publishing-software offerings do not confirm its current service scope or whether they fit your project.
The reported history and ownership trail
The founding year and founders give you useful identity markers, but a historical description does not confirm that a present-day contact has authority to represent the legal entity.
The founders page says Martha and Richard Cichelli owned 100% of Software Consulting Services, LLC from its founding in 1975 until its sale to Kurt Jackson in 2021. A PromptLoop summary likewise says ownership transitioned to Kurt Jackson in 2021 and identifies him as Owner and Managing Member. The same summary names Phil Curtolo as Vice President of Sales and Walt Lafferty as Chief Financial Officer.
The leadership description includes additional timing details: Phil Curtolo is identified as Vice President of Sales and is described as having joined in 2002, while Walt Lafferty is identified as Chief Financial Officer and is described as having joined in 2022. The PromptLoop summary identifies those roles and joining years, but the current status of those positions remains unconfirmed.
Build the ownership trail into your identity check rather than accepting it as a conclusion. Compare the names and roles with current organizational contacts, official filings where available, and the authority of the person who would sign a proposal or contract. Ask for an explanation if the legal name, ownership history, leadership names, or contracting entity differs across records.
It does not replace confirmation of the current legal entity, ownership, or authority to contract.
What each source type can establish
Source provenance changes how you should use a company description. A founders page can document what the organization’s own historical material says about ownership. A directory can supply a lead about location, classifications, workforce, or services. An attributed summary can organize public descriptions, but it may not be the original record. None of those categories should be treated as interchangeable with a current government registration or a direct confirmation of contracting authority.
| Source type | What it can support | Boundary for your decision |
|---|---|---|
| Company or founders material | The organization’s stated history, ownership account, service description, or product relationship | It does not by itself prove current registration status, current leadership, or authority to sign your contract |
| Attributed company summary | A reported location, industry focus, leadership description, or operating profile | Check the original page and date before relying on a material claim |
| Employee or business directory | A search lead, classification entry, approximate workforce range, or profile distribution | Treat estimates as provisional because methods and reference dates may differ |
| Press release or trade-facing profile | The commercial model and capabilities described at the time of publication | Do not assume a 2022 description remains the current offer |
| Official registration or filing | The legal name, jurisdiction, status, and filing details shown by that authority | Match the record to the organization and contracting party before proceeding |
Company-associated pages describe the business’s history and services, while PeopleSmart, LeadIQ, and RocketReach provide directory estimates. These sources do not by themselves confirm the current legal entity. That gap matters because a provider assessment can fail even when the industry description sounds plausible: the name, website, contracting entity, and current operating organization may not align.
Record each assertion with its source category and date. If two sources disagree, preserve both entries until you resolve the difference. Do not turn a repeated directory statement into an independently verified fact simply because it appears on several websites.
Why the reported employee counts cannot establish current size
The reported employee counts conflict, so you should not select one figure as the organization’s current size. The range describes an estimated workforce band, not a confirmed headcount.
LeadIQ’s estimate is one of several conflicting directory figures and does not establish current headcount. Its country distribution lists the United States at 86%, South Africa at 10%, and India at 3% of the employee profiles it assigns by country. The 41 figure measures LeadIQ’s estimated total, while the percentages measure the distribution of its listed profiles; neither establishes the number of current employees, contractors, or active delivery personnel.
The 24 figure is another directory-reported headcount and conflicts with both the PeopleSmart range and the LeadIQ estimate. LeadIQ also reports that business and engineering account for 48% of profiles for which it identifies a department, and that the workforce spans 11 departments. The 48% figure measures profiles with a known department, not the organization’s full workforce or its engineering capacity.
The disagreement has a practical consequence: headcount should be a question for direct confirmation, not a selection exercise. Ask which figure includes employees, contractors, delivery partners, or inactive profiles; request the approximate team available for your engagement; and separate total organizational size from the people assigned to your work.
Use the estimates only to generate questions:
- What is the current delivery team size for the services you need?
- Which roles are employees, contractors, or external partners?
- Where will the assigned team work, and during which time zone or hours?
- Who provides support after implementation?
- Can the proposed team’s names, roles, and availability be tied to the contracting organization?
Until those answers are documented, the organization’s workforce size remains unresolved.
The FotoWare relationship needs direct clarification
One description says the organization resells and supports FotoWare solutions for large asset collections and varied publishing workflows. Inc.com states that Software Consulting Services LLC created the FotoWare digital asset management products. The descriptions conflict, and the organization’s current role - whether it created, owns, resells, or supports the relevant FotoWare products - requires direct clarification.
The distinction matters if your evaluation depends on intellectual-property ownership, implementation authority, support responsibility, product continuity, or the right to modify and integrate the software. “Created,” “resells,” and “supports” describe different commercial and technical roles. You should not treat them as interchangeable.
Inc.com also states that Software Consulting Services LLC has been building, deploying, and servicing technology and software for the news-publishing industry since 1983. The same source says the organization was developing a product that produces fully paginated news pages in 5 to 7 seconds. The 1983 date describes the reported period of industry activity, while the 5-to-7-second figure describes the stated product output time. Because that product description is time-sensitive, ask whether the product exists, remains supported, and applies to your workflow.
Those details can help you route clarification questions, but they do not resolve the FotoWare contradiction.
Request a written explanation covering:
- Whether the organization created, owns, resells, implements, or supports the relevant FotoWare products.
- Which entity holds the customer contract and support obligation.
- Whether the relationship changed over time or concerns different products.
- What licensing, integration, data-hosting, and exit rights apply to your proposed use.
- Which current documentation demonstrates the claimed role.
Keep both descriptions in your record until the organization or an authoritative product record resolves the difference.

Create an entity-verification record before making contact
An entity-verification record gives you a fixed place to compare the name, organization, and claims before you discuss scope or pricing. Create one record for the exact organization you intend to contact, then capture each item with its source, date, and status.
- Legal identity. Record the exact legal name, entity suffix, jurisdiction, registration number, and any names used publicly. Note every variation rather than silently treating similar names as equivalent.
- Registration status. Check the relevant official registry or filing system for the status shown there. Record formation, active, inactive, dissolution, or other status language exactly as displayed, along with the date of the search.
- Registered contact details. Capture the registered agent, registered address, principal business address, domain, email domain, telephone number, and other contact details. Mark each item as a registry entry, website statement, directory entry, or direct confirmation.
- Ownership and authority. Record the reported owner, managing member, officers, and the person authorized to negotiate or sign. Match those names to the entity that would appear on a proposal, order form, invoice, or contract.
- Operating profile. Add the publishing-software services, products, integrations, support model, and customer segment that the organization says it serves. Separate historical descriptions from the current offer.
- Claim status. Label each material item as confirmed, attributed, directory-estimated, disputed, stale, or unresolved. Attach the date and source to every label.
Do not let a completed-looking spreadsheet create false certainty. A field is useful only when you know what source supports it and what that source can establish. If the legal name, domain, address, ownership, or contracting party does not align, pause the provider assessment and resolve the identity mismatch first.

Confirm the details that determine engagement fit
An engagement-fit review should test the actual work, delivery responsibility, and operating conditions rather than relying on an industry label. Once you have an identity record, use direct questions that map the proposed project to the organization’s current capabilities.
Ask about the work itself:
- Which products, modules, or services would address your stated workflow?
- What does the organization build, configure, integrate, host, resell, or support?
- Which capabilities are available now, and which would require new development or a third party?
- What systems, data formats, interfaces, and migration tasks are in scope?
- Who owns the resulting code, configuration, documentation, and operational knowledge?
Ask about delivery:
- Which legal entity would contract with you?
- Who would be accountable for architecture, implementation, testing, support, and escalation?
- Which team members would be assigned, and what roles would they hold?
- What happens when the proposed team member is unavailable or the engagement ends?
- What artifacts define acceptance, handoff, support, and change control?
If your project involves financial or health data, add questions about access boundaries, data handling, audit records, incident escalation, retention, subcontractors, and the specific security or compliance representations being made. Do not accept a sector label as proof of a control or certification. Ask for the exact representation, its scope, the entity it covers, and the document or contract term that governs it.
For a meaningful comparison, write the answers into the same record as the identity findings. A provider can match the name and industry while failing the project because its current product scope, delivery team, support responsibility, or data-handling terms do not match your requirements.
When unresolved identity or capability claims warrant qualified review
Some unresolved questions should stop ordinary provider evaluation because they affect who can bind the organization, what you would receive, or how material project risks would be handled. Escalate the question when any of these conditions remains open:
- The legal name, registration status, ownership, or contracting entity cannot be matched.
- The person offering services cannot demonstrate authority to represent the organization.
- The proposed service depends on a product relationship, license, integration right, or support obligation that has conflicting descriptions.
- Security, privacy, compliance, data handling, or continuity claims are broad but lack a defined scope and responsible entity.
- The proposed team, delivery model, subcontractor role, or support commitment is materially different from the public profile.
- Contract terms affecting ownership, confidentiality, liability, service levels, termination, or data return remain unclear.
Qualified review is especially useful when the unresolved item could change your approval, contracting, security assessment, or implementation decision. Route each question to the person with responsibility for that subject, and preserve the answer with the supporting document or contract language.
Do not solve an identity problem by accepting a lower standard for capability evidence. A plausible location, a recognizable product name, or a directory headcount can support further investigation, but none of them proves authority, suitability, or compliance. If the organization cannot reconcile its name, role, and material claims, keep the status unresolved and do not represent the claim as established.
Proceed only when the identity and fit record is sufficiently supported
Public descriptions associate the name with a Pennsylvania software organization serving newspaper publishing workflows, with reported history, ownership, products, and international use. Confirm the current legal identity, workforce size, FotoWare role, and engagement fit before treating the organization as a potential provider. Treat that combination as a reason to verify, not as a completed provider assessment.
Move forward only when your record connects the exact legal entity to the current contact, contracting authority, services, delivery responsibility, and material security or compliance representations. Keep disputed directory estimates and conflicting product descriptions marked as unresolved until they are reconciled. Have qualified legal, procurement, security, or compliance professionals decide issues within their remit before you rely on a material representation or contract term.
When the identity and fit record supports the project, provide a concise brief containing the verified entity details, required services, target systems, delivery expectations, relevant data conditions, and questions that remain open. That brief gives the organization a defined basis for responding and gives you a cleaner record for deciding whether to continue.
Which company details should a prospective client verify?
Which legal-entity details should be verified?
Confirm the exact legal name, current registration and status, address, ownership, and the entity that would sign an engagement through authoritative records and direct confirmation with the organization.
Which service and location details should be verified?
Confirm whether the organization currently provides the newspaper-publishing, digital-asset-management, and advertising capabilities described in public materials, and verify its operating address in Pennsylvania.
What ownership and contracting details should be checked?
A founders page says Martha and Richard Cichelli owned 100% of the business until its sale to Kurt Jackson in 2021; another summary identifies Jackson as Owner and Managing Member. Confirm current ownership and which entity would sign the engagement and provide support.
How should conflicting workforce estimates be handled?
PeopleSmart, LeadIQ, and RocketReach provide different workforce estimates. Ask what each count includes and what team, roles, and availability would apply to the engagement.
Which source conflict needs clarification before evaluation?
Descriptions of the FotoWare relationship differ: one says Software Consulting Services LLC resells and supports FotoWare solutions, while Inc.com says it created the products. Ask whether the descriptions concern different products or periods and which party handles licensing and support.
What should be checked when the organization makes a compliance claim?
Ask which legal entity the claim covers, what data and services are in scope, and which current documents support any security, privacy, HIPAA, PCI, SOC 2, or other compliance representation.