ITSN's "Dual-Blade" AI development methodology—proven across multiple in-house products—now available for your development team.
From methodology implementation to PoC development outsourcing, we walk alongside you with a proven workflow. Running claude.ai (strategy & design) and Claude Code (implementation & operations) in parallel, with ADR / SESSION-LOG / OFD principles retaining context— all 6 products on this site were developed and shipped using this methodology.
Simply "subscribing to an AI tool" will not improve development productivity. What you need is a development methodology built around those tools, and the operational design of Living Documents to support it. ITSN has proven this methodology through its own product development.
Two services tailored to your situation. If you already have a development team, choose A. If you just need something working first, choose C. You can also combine both to run in-house development and PoC in parallel.
We transfer the Dual-Blade methodology to your development team. Environment setup, ADR/SESSION-LOG operational design, prompt coaching, and pair reviews—monthly support to guide your team toward self-sufficiency.
Best fit: Organizations with an existing development team that want to build AI-driven development as an in-house capability.
Turn an idea into a working PoC in a short timeframe. ITSN handles the entire flow—requirements → design → implementation → deployment—using the Dual-Blade method. We deliver a working product and handoff documentation.
Best fit: Organizations that don't insist on in-house development and simply want something working quickly. Post-PoC maintenance can be handled in-house or by a third party.
claude.ai = PM / Design role: Handles strategic decisions, requirements structuring, prompt drafting, design reviews, and ADR creation assistance. Excels at long-form discussion and comparing multiple options—takes on the "thinking" phase in the browser conversation UI.
Claude Code = Implementation / Operations role: Handles code generation and editing, Git operations, CI/CD, infrastructure operations (terraform, etc.), and test execution. Excels at writing to real environments—takes on the "executing" phase from the CLI.
Living Documents (ADR / SESSION-LOG / OFD principles) for context retention: Prevents context loss when running multiple projects in parallel, and functions as ready-to-use handover documentation when transitioning to in-house development. "How far have we progressed?" and "Why was that decision made?" remain traceable—built alongside development as it evolves.
All of the following are in-house products that ITSN developed and shipped using the methodology presented on this page. They are proof that the Dual-Blade workflow is not a theoretical concept but a method capable of continuously delivering real products.
Credential sharing manager (in-house credential management SaaS).
View product pageMulti-cloud (AWS/Azure/GCP) cost monitoring desktop application.
View product pageICMP/TCP/HTTP network monitor with audio + toast notifications (Windows resident utility).
View product pageSPFx solution for managing completion of Microsoft Teams threads. Teams native notifications.
View product pageMeasure actual radio signals with NetAlly professional instruments → optimize AP placement → deploy Omada.
View product pageWeb tool that instantly provides approximate pricing based on VIGI / Omada product configuration and quantity.
View product pageSpeed reference: The "Wireless LAN Site Survey" page on this site was itself completed—from a 2-hour claude.ai chat to Claude Code auto-deployment in production—in a single workflow. Pages of similar scale and complexity can be shipped in under one business day using the Dual-Blade method.
Architecture Decision Records log key decisions chronologically. "Why was that choice made?" remains traceable. The MailWard project has 23 ADRs—every design decision is recorded.
A cross-session handoff mechanism. Prevents chat histories from growing too long, ensuring no context is lost even when running multiple projects in parallel. Delivered as-is as handover documentation when transitioning to in-house development.
Design is reverse-engineered from the deliverable. Prevents plan bloat and theoretical abstraction, reaching something that works by the shortest path.
Documentation grows alongside development. Never created in bulk after completion—unconfirmed items use TODO markers + version management. Records are maintained without sacrificing development pace.
| Aspect | Traditional | Dual-Blade |
|---|---|---|
| Design Decision Records | Tacit knowledge / scattered | Chronologically logged via ADR |
| Cross-session Continuity | Dependent on chat history | Explicit handoff via SESSION-LOG |
| Initial PoC Delivery Speed | Days to weeks | Hours to days |
| Context Loss Risk | High (caused by long conversations) | Low (permanently preserved via Living Docs) |
| Projects Runnable in Parallel | 1–2 projects | 5+ projects |
Monthly fee + initial consulting. On request based on scope (team size, monthly session frequency, pair review hours). Minimum engagement: 3 months; standard is 3–6 months.
Fixed fee per PoC (varies by scope). Typically 2 weeks–2 months, varying with number of features and integration scope (external APIs, data sources, authentication).
Anthropic ZDR (Zero Data Retention) and claude.ai Enterprise plan (Learning Exclusion Guarantee) options are available upon request. We have experience handling M365 confidential data during MailWard development, and data policies are clearly defined at the time of contract.
* Specific amounts vary significantly by requirements and scope. Please contact us for a quote.
Whether you have questions about the methodology or want to explore what's possible for your organization, feel free to reach out. We also offer live Dual-Blade demonstrations.
