Do you mean the yarn run build command?

If you want to ditch Sage’s build process and just use sass you can go ahead. What you need to know is that main.css does not live in the same directory as main.scss, so the command will need to reflect that. Also, the Sage build process hashes the built files and then tells WordPress the name of the hashed file, not main.css.

Reference this when you set the input and the output of the sass command:

themes/your-theme-name/   # → Root of your Sage based theme
├── dist/        
│   └── styles/           # → the main stylesheet lives in here.
└── resources/        
    └── assets/        
        └── styles/       # → main.scss lives in here

I can’t recommend any of this though.