Bullpen is a Telegram trading bot. Its entire user-facing product surface is a Telegram chat: traders send trade commands to the bot in Telegram and check positions and results in that same chat, while a Bot Operator connects the bot to the trading account and keeps it running, watching bot status and errors.
The product intent is a crypto trading assistant that lives where its users already are — inside Telegram — rather than in a separate web terminal. The reference material at https://app.bullpen.fi/ is used only as domain context for crypto trading features (perpetuals and spot trading, order types, discovery, transfers, funding, non-custodial wallets, and a legacy Telegram bot that lets users paste token addresses, analyze, and trade within Telegram). It does not add web-terminal pages, wallet-login surfaces, or any other capability to this product. The product is a Telegram trading bot.
The audience is crypto traders who want to issue and monitor trades conversationally, and the operator responsible for the bot's connection to the trading account and its runtime health.
Bullpen is delivered as a Telegram bot backed by a shared FastAPI backend process and a MariaDB database for application-owned persistent data. There is no custom web UI: all trader and operator interaction happens on the Telegram provider surface (chat messages, commands, and bot replies). The backend holds the bot's connection to the trading account, executes trade commands received from Telegram, records positions and results, and exposes bot status and error information back into the chat.
Actors:
Accepted behavior in scope: the bot operates in Telegram chat as its user interface; the Bot Operator connects the bot to the trading account; the Trader starts a Telegram chat with the bot; the Trader sends trade commands and checks positions and results in the same chat; the Bot Operator watches bot status and errors.
Narrow exclusions: no first-party web application, no web trading terminal, no in-product wallet creation or key export flows, and no capabilities beyond what the Telegram chat and the operator's connection/status responsibilities require.
Removed from scope
Bullpen's delivery boundary is the Telegram provider surface. Traders and the Bot Operator do not receive a first-party web destination; they interact through Telegram chat with the bot, and the bot's replies are the observable product state. The shared FastAPI backend is the application-owned system of record: it maintains the bot's connection to the trading account, processes trade commands, persists positions and results, and surfaces status and errors. MariaDB stores that application-owned persistent data.
Access follows the provider: Telegram identity is the interaction identity, and the bot is reachable in chat once the Bot Operator has connected it to the trading account. The operator's connection responsibility is a prerequisite for trader journeys, not a separate web console. Nothing in this document establishes differentiated permissions, role-based visibility, or account-management features; the two personas differ by responsibility, not by a permission system described in the sources.
Current horizon: Telegram chat trading commands, position and result reporting in chat, operator connection of the trading account, and operator visibility of bot status and errors. Future ideas from the reference material (web terminal, wallets, on-ramps, discovery, transfers) are not current and are not represented in any page or acceptance criterion.
The page contract for this product is the Telegram bot chat surface. There is no custom first-party page; the single accepted destination is the provider-managed Telegram chat with the bot.
FR-1 — Telegram chat as the product interface (explicit) As a Trader, I should interact with Bullpen entirely inside a Telegram chat, so that I can trade without leaving Telegram.
FR-2 — Start a chat with the bot (required_inference) As a Trader, I should start a Telegram chat with the bot, so that I have a channel to issue commands and receive results.
FR-3 — Send trade commands in chat (explicit) As a Trader, I should send trade commands to the bot in Telegram, so that trades are executed on my behalf.
FR-4 — Check positions and results in the same chat (explicit) As a Trader, I should check my positions and results in the same Telegram chat, so that I can monitor outcomes without another tool.
FR-5 — Connect the bot to the trading account (required_inference) As a Bot Operator, I should connect the bot to the trading account, so that trader commands can be executed.
FR-6 — Keep the bot running and watch status and errors (explicit) As a Bot Operator, I should watch bot status and errors, so that the bot stays available for traders.
The product has no first-party visual surface; its presentation is the Telegram chat. The only visual constraints are those of the Telegram provider: the bot's messages render in the user's Telegram theme, and message formatting (text, emphasis, structured position/result listings) should be legible in both light and dark Telegram themes. No custom palette, font, or layout is specified by the user, and none is invented here.
The signature concept is conversational clarity: every bot reply is a compact, scannable chat message — a confirmation, a position/result listing, a status line, or an error — formatted so a trader can read the outcome at a glance inside Telegram. This recomposes only accepted content (commands, confirmations, positions, results, status, errors) and introduces no new behavior or destination.
Interaction Model: Static (direction) Motion Tempo: still Hero Dimensionality: flat
Landing Hero Motion Brief: Not applicable — there is no first-party landing page. The entry experience is the Telegram chat itself: the Trader opens the chat and the bot's first reply is the composed first frame. There is no motion beyond Telegram's native message delivery; the reduced-motion state is identical because no custom animation is used.
backend and database services; no additional services are required for the accepted workflows.https://app.bullpen.fi/ supplies crypto trading domain context only; its web-terminal, wallet, on-ramp, discovery, and transfer features are not current product scope.No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!