BulBul SEQS

BulBul SEQS is a self-reported project by Jeevanjot Singh, a solo developer, that aims to create an application for filing cumulative period summaries using HMRC’s Income Tax Self Assessment (ITSA) APIs. The app is built with Amplify and SwiftUI, and integrates OAuth2 flows and token management. It is described as a functional prototype developed in the context of a hackathon, with no evidence of revenue, customers or traction.

The project appears to be an early-stage technical experiment focused on automating tax filing through MTD (Making Tax Digital) APIs. The author states that it supports viewing records, editing them, fetching obligations, and submitting summaries — all within a test environment.

The description states:

• BulBul SEQS is an app that allows users to create and submit cumulative period summaries using ITSA APIs from HMRC.
• It supports viewing business records, editing them, and fetching obligations.
• It integrates with MTD APIs and uses OAuth2 for authentication.
• The app is built using Amplify (backend) and SwiftUI (frontend), targeting macOS and iOS platforms.

Inference: Based on the author's own description, this appears to be a prototype tax filing tool intended for UK-based business owners or developers working with HMRC’s MTD framework. It is not yet a commercial product but rather an experimental build.

The author claims:

• The app enables easier and more automated tax filing via integration with HMRC's APIs.
• It aims to innovate in the tax filing process by leveraging advancements made possible through MTD.
• It was inspired by the need to avoid third-party software for CT600 filings, and extended to income tax returns.

Inference: The positioning is that of a developer-driven prototype aiming to simplify tax compliance using digital tools. There is no evidence of market positioning or branding beyond the author’s personal motivation.

The description states:

• The app targets individuals who file income tax returns in the UK.
• It was initially inspired by the need for a better way to handle CT600 filings, and later expanded to include income tax.
• The user base is likely UK-based business owners or freelancers using HMRC’s MTD framework.

Inference: The ICP (Ideal Customer Profile) seems to be UK-based self-employed individuals or small business owners who are already using or planning to use HMRC's MTD APIs. However, no evidence of actual customers or user feedback exists.

Not evidenced.

The description does not mention any pricing model, monetization strategy, or commercial intent beyond the author’s personal development goals.

The description states:

• Built with Amplify, Cognito, Lambda, and data storage plugins.
• Frontend built using SwiftUI for cross-platform support (macOS and iOS).
• Uses OAuth2 flow, access/refresh tokens, and fraud prevention headers.
• Developed over a short time frame during a hackathon.
• Utilizes Codex for code generation.

Inference: The technical stack suggests a modern, cloud-native approach with a focus on API integration. However, the prototype is described as incomplete (e.g., lacks testing, design polish), and no production deployment or scalability details are provided.

Not evidenced.

There is no evidence of:

• Revenue
• Customers
• User adoption
• Product-market fit
• Any kind of traction beyond the prototype stage

The project is described as a test environment app with basic functionality, developed in a hackathon setting.

Not evidenced.

No information is provided about existing competitors or market players in the UK tax filing automation space. The author does not reference any similar tools or platforms.

• Solo developer project: No team or external support, which raises concerns around long-term maintenance and scalability.
• Prototype only: No evidence of real-world usage or integration beyond a test environment.
• No commercialization plan: No mention of monetization, pricing, or go-to-market strategy.
• Unverified claims: All statements are self-reported and unverified; no third-party validation exists.

Inference: The project is at an early stage with limited commercial viability. It may be a proof-of-concept rather than a scalable product.

1. What is the current status of integration with HMRC APIs? Is it fully functional in live mode?
2. Are there any known limitations or bugs in the prototype that prevent real-world use?
3. Has the author considered legal or compliance risks associated with tax filing automation?
4. What are the plans for expanding beyond the test environment and into production?
5. How does the app handle data security, especially when dealing with sensitive financial information?