Plasmonic Coupling Simulator

The company appears to be a solo developer project named Plasmonic Coupling Simulator, self-described as a local, bilingual web application for simulating optical spectra from gold nanoparticle assemblies. The author states it uses Mie and Coupled Dipole Approximation methods with QCM tunnel parameter tables, and is built using Python, FastAPI, JavaScript, and Plotly.js.

The project is described as a tool for students and early-stage researchers to explore geometry-dependent optical responses before moving to higher-fidelity numerical methods. It supports 1–20 Au nanospheres, offers 3D visualization, and allows users to vary gaps and wavelengths.

What changed: The author reports iterative development using GPT-5.6 and Codex for analysis, implementation, testing, and documentation, with human review maintaining scientific scope and product decisions.

The single most important open question: Is there any evidence of user adoption or commercial traction beyond the author’s own use-case? The description states no revenue, customers, or usage data exist.

Note: This is a self-reported, unverified account. All claims are based on the author's own description and have not been independently corroborated.

• The description states that Plasmonic Coupling Simulator is a local, offline-capable web application.
• It is designed for assemblies of 1 to 20 Au nanospheres.
• Users can start from editable presets (dimer, trimer, random cluster), inspect geometry in a real-diameter 3D preview, and calculate extinction, scattering, and absorption spectra.
• Results can be downloaded as CSV or JSON, including metadata like calculation conditions, timestamps, warnings, and QCM provenance.
• The interface supports English and Japanese with state persistence across language switches.
• It uses Mie calculations for single-particle reference and a retarded Coupled Dipole Approximation (CDA) for multi-particle assemblies.
• For surface gaps from 0.5 to 1.0 nm, it selects a limited Quantum Corrected Model (QCM) path.
• The QCM tunnel parameter table is described as a manual digitization of Esteban et al. (2012), Fig. 2d, with estimated reading uncertainty.
• It blocks gaps below 0.5 nm and distinguishes QCM status from classical CDA warning ranges.
• The stack includes: Python, FastAPI, JavaScript, Plotly.js, Server-Sent Events.
• The app binds only to localhost and works offline after setup.

Inference: The tool is a research or educational aid, not a commercial product. It does not appear to be a SaaS offering or a product for general public use.

• The author states the goal is not to replace rigorous methods like BEM, DDA, FDTD, or TDDFT.
• Instead, it helps users inspect particle layouts, vary gaps and wavelengths, and make model assumptions visible.
• It is positioned as a lightweight local tool for early-stage exploration before moving to higher-fidelity numerical methods.
• The author describes the tool as a way to “move quickly from an intuitive geometry” to reproducible spectrum calculation.
• The project was submitted to the OpenAI 2026 hackathon, suggesting it is a prototype or proof-of-concept.

Claim: The tool is for students and early-stage researchers.

Inference: It is not positioned as a commercial product or enterprise solution.

• The description states the tool is intended for students and early-stage researchers.
• It is designed to help users move from intuitive geometry to reproducible spectrum calculation.
• No specific customer segments, personas, or use cases beyond academic or research settings are described.
• There is no evidence of targeting commercial customers, institutions, or end-users outside of the research domain.

Not evidenced: No explicit ICP (Ideal Customer Profile) or defined buyer personas.

• The description does not mention any pricing, licensing, or monetization strategy.
• It is described as a local, offline-capable web application that binds only to localhost.
• No evidence of a SaaS model, subscription, or paid features is present.
• There is no indication of revenue streams or commercial viability.

Not evidenced: No business model or pricing information.

• The tool uses Mie calculations, retarded Coupled Dipole Approximation (CDA), and a limited Quantum Corrected Model (QCM) for surface gaps.
• It includes 3D visualization using real-diameter mesh-based preview in nanometre coordinates.
• The UI supports browser-side CSV/JSON export.
• It uses GPT-5.6 and Codex for iterative development, analysis, testing, and documentation.
• Human review remains responsible for scientific scope, physical-model limits, product decisions, and final acceptance.
• The application is built with Python, FastAPI, JavaScript, Plotly.js, Server-Sent Events.
• It works offline after setup and binds only to localhost.

Inference: The tool is a technical prototype with strong engineering execution but not yet a commercial product.

• The project was submitted to the OpenAI 2026 hackathon, indicating it is a prototype or proof-of-concept.
• No evidence of user adoption, customer base, or usage metrics beyond the author’s own use-case.
• There is no mention of revenue, customers, or product traction.
• The author reports iterative development and browser testing issues that were resolved.

Not evidenced: No traction, adoption, or maturity indicators beyond self-reported development process.

• The description does not reference any direct competitors.
• It is positioned as a tool for early-stage exploration, not replacement of rigorous numerical methods like BEM, DDA, FDTD, or TDDFT.
• No mention of existing tools in the plasmonics simulation or nanophotonics space.

Not evidenced: No competitive landscape or market positioning beyond self-description.

• The tool is described as a solo developer project, with no team or organizational structure.
• It is not a SaaS product and does not appear to be monetized.
• There is no evidence of user adoption or commercial traction.
• The tool is local-only, which limits scalability or distribution.
• The author explicitly states that AI-generated output was not treated as evidence for physics, experimental values, or literature claims — raising questions about scientific rigor.

Inference: The project may be a research prototype with limited commercial potential or scalability.

1. What is the intended user base beyond personal use?
2. Are there any plans to commercialize this tool, and if so, how?
3. How does the tool’s accuracy compare to established solvers like FDTD or BEM?
4. Has the author considered broader material support or size-dependent damping?
5. Is there a plan for automated UI testing or browser compatibility beyond local development?
6. What are the limitations of the QCM model used, and how were they validated?

Note: These questions are based on the self-reported description and aim to uncover gaps in evidence.